Description of problem: During deployment of the overcloud, the nodes are NOT registered to RHSM. Version-Release number of selected component (if applicable): 7.1 How reproducible: Every Steps to Reproduce: 1. Deploy using this command: openstack overcloud deploy \ -t 120 \ --templates ~/templates \ -e ~/templates/overcloud-resource-registry-puppet.yaml \ -e ~/templates/ceph-wipe-environment.yaml \ -e ~/templates/network-environment.yaml \ -e ~/templates/storage-environment.yaml \ -e ~/templates/pre-and-post-hooks-environment.yaml \ --control-scale 3 \ --compute-scale 13 \ --ceph-storage-scale 4 \ --control-flavor control \ --compute-flavor compute \ --ceph-storage-flavor ceph-storage \ --ntp-server 10.5.26.10 \ --neutron-network-type vxlan \ --neutron-tunnel-types vxlan \ --libvirt-type kvm \ --rhel-reg \ --reg-method portal \ --reg-org <my org key> \ --reg-activation-key <my activation key name> \ --reg-force Actual results: [root@overcloud-controller-0 ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Unknown Expected results: [root@overcloud-controller-0 heat-admin]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Current Additional info:
There are options for the CLI to register to satellite or CDN. See the rhel-reg options here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/appe-Deployment_Parameters.html
Sorry, misread the bug. Reopening...
Created attachment 1103966 [details] pre-and-post-hooks-environment.yaml
Created attachment 1103967 [details] storage-environment.yaml
Created attachment 1103968 [details] network-environment.yaml
Created attachment 1103969 [details] ceph-wipe-environment.yaml
Created attachment 1103970 [details] overcloud-resource-registry-puppet.yaml
can you retry the deployment command and pass this as the last -e argument: -e ~/templates/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml
(In reply to James Slagle from comment #9) > can you retry the deployment command and pass this as the last -e argument: > > -e > ~/templates/extraconfig/pre_deploy/rhel-registration/rhel-registration- > resource-registry.yaml i confirmed with dan that this did work. the issue here is with passing overcloud-resource-registry-puppet.yaml via -e, as that is going to override any environment setting done by the client. In the case of rhel registration, the client automatically sets NodeExtraConfig to rhel-registration.yaml, but when you include overcloud-resource-registry-puppet.yaml on the cli, then that gets overwritten.
Additionally, rhel_reg_repos is not set in templates/extraconfig/pre_deploy/rhel-registration/environment-rhel-registration.yaml. Should this be set to the default set of repos that customers get with an RHOS subscription?
AFAICT, these repos should be enabled by default: rhel-7-server-rpms rhel-7-server-rh-common-rpms rhel-7-server-openstack-7.0-rpms rhel-7-server-rhceph-1.3-calamari-rpms rhel-7-server-rhceph-1.3-mon-rpms rhel-7-server-rhceph-1.3-osd-rpms rhel-7-server-rhceph-1.3-tools-rpms I think they should get added to extraconfig/pre_deploy/rhel-registration/environment-rhel-registration.yaml
(In reply to Dan Yocum from comment #12) > AFAICT, these repos should be enabled by default: > > rhel-7-server-rpms > rhel-7-server-rh-common-rpms > rhel-7-server-openstack-7.0-rpms Yes, might also need rhel-7-server-openstack-7.0-director-rpms, but not sure > rhel-7-server-rhceph-1.3-calamari-rpms No -- we don't include calamari > rhel-7-server-rhceph-1.3-mon-rpms > rhel-7-server-rhceph-1.3-osd-rpms > rhel-7-server-rhceph-1.3-tools-rpms Optional. Some customers won't have ceph entitlements, so won't have these repos to enable. Maybe enable them if available, but not if not available. > > I think they should get added to > extraconfig/pre_deploy/rhel-registration/environment-rhel-registration.yaml
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
This seems to be resolved.