Description of problem: During the upgrade from OSP12 to OSP13 Director didn't registered correctly the overcloud nodes, the following steps where followed, but upgrade failed because overcloud was still using OSP12 channel https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/upgrading_red_hat_openstack_platform/assembly-preparing_for_overcloud_upgrade#upgrading_the_overcloud_registration_details Perhaps the problem is here <snip> RHELRegistrationActions: type: comma_delimited_list default: - CREATE description: Actions when the system profile will be registered, by default we only do this on CREATE of a new server, not for existing nodes. </snip> Perhaps including this during the upgrade process would workaround the issue, but not tested environment-rhel-registration.yaml parameter_defaults: RHELRegistrationActions: ['CREATE', 'UPDATE'] Version-Release number of selected component (if applicable): OSP12 to OPS13 How reproducible: Steps to Reproduce: 1. Deploy OS12 2. follow provided steps to upgrade 3. Actual results: Upgrade fails, overcloud nodes still subscribed to 12 Expected results: overcloud subscribed to 13, upgrade success
*** Bug 1663886 has been marked as a duplicate of this bug. ***
We have two issues here: * First one should be fixed by a documentation BZ. As we created the rhel-registration/ folder from the osp12 templates, the content of the scripts/resources is not updated (we run "overcloud upgrade prepare" with osp13 templates but rhel-registration/* templates belong to osp12). We should add a pre-requisite in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/upgrading_red_hat_openstack_platform/assembly-preparing_for_overcloud_upgrade#upgrading_the_overcloud_registration_details to ensure that the templates and scripts are updated from /usr/share/openstack-tripleo-heat-templates/extra_config/pre_deploy/rhel-registration + Some helpful command could be: cp -r /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/rhel-registration* /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/scripts/ ~/templates/rhel-registration/ * The second issue is indeed a bug which should get fixed by https://review.openstack.org/#/c/633026/1 , during the upgrade we're setting the rhel_reg_force heat parameter to True to force a re-registration (otherwise subscription-manager will fail as the node is already registered) but as ~/templates/rhel-registration/environment-rhel-registration.yaml assigns a value for that same parameter rhel_reg_force: "", it gets overwritten and as a consequence it doesn't force the registration and the upgrade starts with the older osp12 repositories.
Hi!! We have drafted a simple guide about how to reproduce this issue and how to verify that is actually working fine. If you want to verify it by yourself follow http://etherpad.corp.redhat.com/verify-osp12-foobar If you want to reproduce the error, just skip the rhos-release step in the Undercloud.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0939