Bug based on BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1522960 [which references to OSP 11 to OSP12) but I believe we're having the same issue in master right now. So we need to fix this from stable/pike to master (notice that stable/pike used the rhos-environment script, while since stable/queens we started using OS::TripleO::Service::Rhsm service.
Description of the problem:
- When registering the nodes via satellite or RH portal, the repositories do not get updated on upgrade.
- Register nodes during deployment either using rhel-registration script filling in rhel-registration/environment-rhel-registration.yaml (Pike/Queens) or passing an environment file with the corresponding values for the Rhsm service as stated in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/advanced_overcloud_customization/ansible-based-registration (Rocky/Master)
- Update rhel_reg_repos (Pike/Queens) or rhsm_repos if (Rocky/Master)
- Perform upgrade to next release
- Go into overcloud nodes and check the enabled repos via subscription-manager repos --list-enabled
- The very same repos which were enabled in deploy remain enabled and the new ones are not configured.
***This LP aims to cover multiple releases***
Related fix proposed to branch: stable/pike /review. openstack. org/609422
Review: https:/