Overcloud registration with portal fails

Latest response


I would like to register the openstack nodes using the portal when deploying with openstack-director.
I added the environment files as described in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/advanced_overcloud_customization/#sect-Registering_the_Overcloud

rhel_reg_auto_attach: "true"
rhel_reg_activation_key: "my-openstack"
rhel_reg_org: "1234567"
rhel_reg_pool_id: "1a85f9223e3d5e43013e3d6e8ff506fd"
rhel_reg_repos: "rhel-7-server-rpms rhel-7-server-extras-rpms rhel-7-server-rh-common-rpms rhel-ha-for-rhel-7-server-rpms rhel-7-server-openstack-10-rpms rhel-7-server-rhceph-2-osd-rpms rhel-7-server-rhceph-2-mon-rpms"
rhel_reg_method: "portal"
rhel_reg_sat_repo: ""
rhel_reg_base_url: ""
rhel_reg_environment: ""
rhel_reg_force: ""
rhel_reg_machine_name: ""
rhel_reg_password: ""
rhel_reg_release: ""
rhel_reg_sat_url: ""
rhel_reg_server_url: ""
rhel_reg_service_level: ""
rhel_reg_user: ""
rhel_reg_type: ""
rhel_reg_http_proxy_host: ""
rhel_reg_http_proxy_port: ""
rhel_reg_http_proxy_username: ""
rhel_reg_http_proxy_password: ""

But I got the following error
2017-05-04 11:36:19Z [overcloud]: CREATE_FAILED Resource CREATE failed: resources[0]: resources.Compute.Property error: resources.NodeExtraConfig.properties: Property rhel_reg_base_url not assigned

I than updated the environment file by setting
rhel_reg_base_url: "https://cdn.redhat.com"

But than I got the following error

CREATE_FAILED Resource CREATE failed: resources[0]: resources.Compute.Property error: resources.NodeExtraConfig.properties: Property rhel_reg_environment not assigned

Any idea what value I should set for rhel_reg_environment???

Furthermore according to overcloud registration document in the link above these values don't need to be set.



Hi Sam,

I'll follow up with you over email.


Hi folks,

I worked with Sam to diagnose the issue. An issue I encountered was that subscription-manager reported an error if using the --auto-attach with an activation key (which makes sense since the activation key defined what subscriptions to attach). This caused the stack to retry the registration script multiple times until it reached the maximum and then failed. I tested both with and without the rhel_reg_auto_attach and was only able to successfully deploy without it.

So if you're using the rhel_reg_activation_key option, you can't use the rhel_reg_auto_attach option.

The docs also included examples that had both these options set, which is incorrect. I've now updated the examples in the docs to remove the rhel_reg_auto_attach parameter and only use rhel_reg_activation_key. For example:

Example 1: Registering to the Customer Portal

A big thank you to Sam Monderer for raising this issue!

Thanks for that Dan!