Red Hat Bugzilla – Bug 1290226
[Director] overcloud systems are not registered to RHSM during deployment
Last modified: 2016-02-29 20:32:08 EST
Its only during the update and is related to usage of overcloud-resource-registry-puppet.yaml. Including this in the update command causes the problem.
but if you remove it (as below), the update works as expected:
$ openstack overcloud update stack osp72r1 -i --templates ~/templates/my-overcloud -e ~/templates/my-overcloud/environments/network-isolation.yaml -e ~/templates/network-environment.yaml -e ~/templates/storage-environment.yaml -e ~/templates/pre-deployment.yaml -e ~/templates/post-deployment.yaml
In the Red Hat documentation https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Updating_the_Overcloud.html#sect-Updating_the_Overcloud_Packages it is mentioned to include "overcloud-resource-registry-puppet.yaml" Heat template.
Perhaps this is a doc bug?
You probably saw the email thread. So the problem is the lack of the RHSM/Satellite information, which you need to also include as an environment file along with "overcloud-resource-registry-puppet.yaml". If this information isn't included, the director concludes that the Overcloud environment does not contain registration and as a result unregisters the nodes.
I'll include a line in the doc to also include the registration environment file during the update.
This content is now live on the Customer Portal:
Closing this BZ. If changes are required, feel free to reopen.