Bug 1265125

Summary:	[RFE] Allow activation keys to enable product repos regardless of whether there is a subscription attached or not
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Activation Keys	Assignee:	Tom McKay <tomckay>
Status:	CLOSED ERRATA	QA Contact:	Bruno Rocha <rochacbruno>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1.2	CC:	ahumbe, alosadag, aperotti, arahaman, bbuckingham, bkearney, brcoca, dgupte, dlobatog, egolov, ehelms, fchoudhry, fgarciad, jcallaha, jentrena, jfenal, jko, jsherril, karnsing, katello-bugs, ktordeur, matthew.lesieur, mharris, mmccune, mmello, mpicoto, mwade, nitthoma, pdwyer, rjerrido, rochacbruno, snemeth, sokeeffe, tomckay, wpinheir
Target Milestone:	Unspecified	Keywords:	FutureFeature, PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 12:32:18 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1479962

Comment 19 Justin Sherrill 2016-01-20 20:13:19 UTC

Note there is a workaround for this:

1) Create two activation keys  Key "A" and Key "B", assign them both to the same lifecycle environment and content view
2) Assign no subscriptions to Key A
3) Assign a VDC subscription or some other subscription to Key B that provides content.  This subscription does not even need to have any free entitlements available
4) Adjust the enabled content on Key B
5) Register a client with  --activationkeys=A,B

The guest will use Key A to auto heal itself grabbing the guest subscription and then use Key B to grab the list of enabled repos.

Comment 20 Bryan Kearney 2016-07-08 20:19:58 UTC

Per 6.3 planning, moving out non acked bugs to the backlog

Comment 22 Tom McKay 2016-09-15 19:27:56 UTC

Created redmine issue http://projects.theforeman.org/issues/16574 from this bug

Comment 23 Bryan Kearney 2016-09-15 20:10:58 UTC

Upstream bug component is Content Management

Comment 24 Bryan Kearney 2016-09-21 18:10:06 UTC

Upstream bug component is Activation Keys

Comment 25 Sean O'Keeffe 2016-09-29 09:27:59 UTC

Another way to workaround this is to add a sub to the activation key then enable/disable Product Content and then remove the sub from the activation key, this will still mean the options you set under Product Content will still be there you just can't change them unless you have a subscription attached to the activation key.

Comment 27 Julio Entrena Perez 2016-11-01 16:14:38 UTC

Workaround in comment 25 seems to work, thank you Sean!

Comment 40 Bruno Rocha 2017-11-02 18:17:39 UTC

Addressed by Organization Level Content Access

https://bugzilla.redhat.com/show_bug.cgi?id=1498158

Comment 46 errata-xmlrpc 2018-02-21 12:32:18 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.

https://access.redhat.com/errata/RHSA-2018:0336