Hi, When using TripleO command openstack overcloud deploy with any of the satellite options, we can see in the code that it actually does this by leveraging the heat resource OS::TripleO::NodeExtraConfig https://github.com/openstack/tripleo-heat-templates/blob/master/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml#L2 The documentation we give users however tells them they can use OS::TripleO::NodeExtraConfig to extend and apply their own arbitrary configuration across all nodes. So if a user passes the rhel registration parameters to the overcloud deploy command, and then supplies their own implementation of OS::TripleO::NodeExtraConfig, then only 1 wins (usually the users work), meaning you silently never get registration happening, with no feedback on why, leaving the user very confused. The rhel registration stuff should be moved to its own resources (and set to none when not used) Regards, Graeme
The request doesn't fit with our plan, we moved the RHSM workflow to Ansible: https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/rhsm.html