Red Hat Bugzilla – Bug 1311859
Satellite repositories should not be forcibly disabled
Last modified: 2017-07-24 11:01:12 EDT
Description of problem:
The rhel-registration script in /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/scripts/ forcibly disables the repository rhel-7-server-rh-common-rpms
When an OverCloud node is registered to an Red Hat Satellite 6, it's presumably to enable life-cycle management of the software on the node. I.e. to enable the ability to publish a Content View and thereby ensuring that consistent and updated repositories are available to the OverCloud nodes. Which repositories are made available is typically controlled by the administrator in the Aktivation Key (specified in rhel_reg_activation_key).
The problem is that the above mentioned script, on line 127, forcibly disables the repository rhel-7-server-rh-common-rpms. With this repository disabled, no errata related to any package in this repository, e.g. cloud-init, can be published to an OverCloud node.
Version-Release number of selected component (if applicable):
*** Bug 1311856 has been marked as a duplicate of this bug. ***
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
we don't plan on fixing this specific issue for OSP 7, and as of OSP 8 we no longer disable this repo:
True, rhel-7-server-rh-common-rpms is no longer disabled but instead, in OSP8, rhel-7-server-satellite-tools.6.1.rpms is forcibly disabled.
This again happens in /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/scripts/rhel-registration on line 131 where $satellite_repo is disabled.
And satellite_repo defaults to rhel-7-server-satellite-tools.6.1-rpms in /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/environment-rhel-registration.yaml.
True, one can easily work around this problem by overriding rhel_reg_sat_repo with an empty string and ensure that the correct repos are set in the activation key. Nevertheless, if a package has been installed from a repository, the repository should not be disabled as it makes life-cycle management of those packages cumbersome.