Bug 1311859 - Satellite repositories should not be forcibly disabled
Summary: Satellite repositories should not be forcibly disabled
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
Target Milestone: Upstream M2
: 12.0 (Pike)
Assignee: Ben Nemec
QA Contact: Alexander Chuzhoy
: 1311856 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2016-02-25 08:39 UTC by David Juran
Modified: 2018-02-05 19:02 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170419202046.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-12-13 20:40:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1673116 0 None None None 2017-07-12 21:45:10 UTC
OpenStack gerrit 446014 0 None None None 2017-07-12 21:46:11 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description David Juran 2016-02-25 08:39:56 UTC
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):

Comment 2 Mike Burns 2016-02-25 12:50:47 UTC
*** Bug 1311856 has been marked as a duplicate of this bug. ***

Comment 3 Mike Burns 2016-04-07 21:11:06 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 6 James Slagle 2016-10-12 13:47:57 UTC
we don't plan on fixing this specific issue for OSP 7, and as of OSP 8 we no longer disable this repo:

Comment 7 David Juran 2016-10-20 14:58:00 UTC
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.

Comment 9 Alexander Chuzhoy 2017-11-29 17:19:23 UTC


Completed a deployment with sat6.
Checking the repos on OC nodes:

<one more repo with rhos12 content>

rhel-7-server-rh-common-rpms is there.
rhel-7-server-satellite-tools-6.2-rpms is there.

grep common /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/scripts/rhel-registration
 returns nothing.

Comment 12 errata-xmlrpc 2017-12-13 20:40:44 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.