Bug 1376020

Summary: 00-rhel-registration Should Support Both Satellite 5 and Satellite 6
Product: Red Hat OpenStack Reporter: Benjamin Schmaus <bschmaus>
Component: diskimage-builderAssignee: Ben Nemec <bnemec>
Status: CLOSED WONTFIX QA Contact: Alexander Chuzhoy <sasha>
Severity: medium Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: bschmaus, jcoufal, jslagle, mburns, morazi, rhel-osp-director-maint, tquinlan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-01 15:42:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Benjamin Schmaus 2016-09-14 13:01:00 UTC
Description of problem: 

The current 00-rhel-registration script only supports Satellite 6 yet we have committed to some customers who rely on Satellite 5 and hence the case statement below only supports subscription-manager syntax and not the Satellite 5 rhnreg_ks syntax for registration.

/usr/share/diskimage-builder/elements/rhel-common/pre-install.d/00-rhel-registration:

...
    satellite)
        # Save an unmodified copy of the repo list for logging
        user_repos=$repos
        repos="$repos --enable ${satellite_repo}"
        echo "Installing satellite dependencies"
        rpm -Uvh "$REG_SAT_URL/pub/katello-ca-consumer-latest.noarch.rpm" || true
        echo "Registering with options: $sanitized_opts"
        subscription-manager register $opts
        echo "Enabling repos: $user_repos"
        subscription-manager $repos
        echo "Disabling satellite repo because it is no longer needed"
        subscription-manager repos --disable ${satellite_repo}
        ;;
...

We need 2 case statements, one for satellite and one for satellite5.


Version-Release number of selected component (if applicable):
OSP9

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Can only register against SAT6

Expected results:
Should be able to register against both SAT5 and SAT6

Additional info:

Comment 3 Ben Nemec 2016-09-14 14:46:41 UTC
Is this because they want to rebuild their overcloud images?  If it's only for deployment, we already have support because we moved the rhel registration bits into tripleo-heat-templates: https://github.com/openstack/tripleo-heat-templates/blob/master/extraconfig/pre_deploy/rhel-registration/scripts/rhel-registration#L123

That has supported sat5 for a long time (since OSP 7 I think).  We could copy that into the dib script, but since we don't normally support rebuilding the image I'm not sure it makes sense to.

Comment 4 Benjamin Schmaus 2016-09-14 15:03:37 UTC
@Ben from Ben,

So in this use case here, they want to rebuild their images and add support for additional tooling.  In this case the HP Proliant tools so that they can do cleaning and RAID configuration on the hosts via IPA.   Does the above still satisfy that requirement, I was under the impression it is only for deploy and not image rebuild.

Comment 5 Mike Burns 2016-09-14 15:06:48 UTC
(In reply to Benjamin Schmaus from comment #4)
> @Ben from Ben,
> 
> So in this use case here, they want to rebuild their images and add support
> for additional tooling.  In this case the HP Proliant tools so that they can
> do cleaning and RAID configuration on the hosts via IPA.   Does the above
> still satisfy that requirement, I was under the impression it is only for
> deploy and not image rebuild.

To be clear -- they need a support exception for rebuilding images.  We do not currently support any images that don't start from our provided images.

Comment 6 Benjamin Schmaus 2016-09-28 12:12:30 UTC
@Mike - I am not sure we have been requiring a support exception for customers here.   I have seen it mentioned from others internally that no support exception is needed.  Further if the customer is using the supported private image as the starting point, I am not sure why one would be needed.

Can you confirm?

Comment 11 Red Hat Bugzilla Rules Engine 2017-02-14 14:07:02 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.