Bug 1116069 - Additional repositories defined in activation key aren't enabled by subscription-manager at registration
Summary: Additional repositories defined in activation key aren't enabled by subscript...
Keywords:
Status: CLOSED DUPLICATE of bug 1132790
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Christine Fouant
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1109802
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-03 16:34 UTC by Stephen Benjamin
Modified: 2017-02-23 21:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-14 18:23:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephen Benjamin 2014-07-03 16:34:18 UTC
Description of problem:
Subscription Manager < 1.10 doesn't enable Red Hat repositories that are enabled in the AK other than the default base repo.  This means puppet won't get installed.

Workaround - add this to the end of the "subscription_manager_register" provisioning template: 

# Enable RH Common for Puppet Support
subscription-manager repos --enable rhel-<%= @host.operatingsystem.major -%>-server-rh-common-beta-rpms


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

How reproducible:
Always

Steps to Reproduce:
1.Create a Content View with the RH Common Beta and normal Base repos
2.Publish the CV
3.Assign it to an activation key
4.Set "Override to Yes" for the RH Common Beta product

Actual results:
The RH Common Beta repo is not enabled on the server, puppet doesn't get installed in kickstart %post

Expected results:
The repo is enabled, puppet installed in %post

Additional info:
Allegedly this is due to RHEL 6 having Subscription Manager 1.9.

Comment 1 RHEL Program Management 2014-07-03 17:32:36 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Christine Fouant 2015-01-14 18:23:43 UTC

*** This bug has been marked as a duplicate of bug 1132790 ***


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