Bug 1122274

Summary:	Consider not showing Products under Activation key subscription choices that only have puppet/docker/file repos
Product:	Red Hat Satellite	Reporter:	Shannon Hughes <shughes>
Component:	Activation Keys	Assignee:	David Davis <daviddavis>
Status:	CLOSED NEXTRELEASE	QA Contact:	Perry Gagne <pgagne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.3	CC:	bbuckingham, bhamrick, mmccune, riehecky, xdmoon
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:03: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:	1115190

Description Shannon Hughes 2014-07-22 20:17:46 UTC

Description of problem:

I created a Product named My-Puppets as a container to hold a Puppet Type repo. I then created a Activation Key. Under the Subscriptions tab of the activation key I see that I can add the My-Puppets as a unlimited subscription. Mentioned this to jsherrill and we both came to conclusion that we probably should not be displaying Products as subscriptions under activation keys that only contain puppet repos.

Comment 1 RHEL Program Management 2014-07-22 20:24:17 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 Brad Buckingham 2014-07-23 19:59:34 UTC

We should address this for both Activation Keys and Content Hosts.

Comment 4 Mike McCune 2015-03-12 22:46:57 UTC

This is not a blocker, clearing flag

Comment 6 David Davis 2016-09-06 12:46:26 UTC

This bug is a bit outdated. I think we now want to hide products with docker, file, and puppet only content.

Comment 7 Bryan Kearney 2016-09-23 00:02:31 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16588 has been resolved.

Comment 10 Bryan Kearney 2017-08-01 20:03:18 UTC

The fix to this bug will be delivered with release 6.3 of Satellite.