Bug 1033314

Summary:	[RFE] Add logic to prefer beta subscription (if available) when auto-attaching on beta version of RHEL
Product:	Red Hat Enterprise Linux 7	Reporter:	Matt Reid <mreid>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED NOTABUG	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	ckozak
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-03 16:33:35 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:	863175

Description Matt Reid 2013-11-21 20:45:05 UTC

Description of problem:
It would be nice if when we had beta programs where people are running beta versions of RHEL, that auto-attaching subscriptions using subscription manager was smart enough to use their beta subscriptions before using up their production subscriptions.

Could we leverage the new distribution.version.modifier to know when to do that?

Would make it much simpler than forcing people to manually attach the beta subscription, or rolling the dice with auto-attach and removing any production subscription that gets pulled in.

Comment 1 Carter Kozak 2013-11-22 14:26:59 UTC

I don't think that's a good idea.  It sounds like we should have a separate beta product cert that is covered by beta product subscriptions.

We only want to use these "beta subscriptions" on the rhel OS product, which seems weird.  I'm not sure how to tell if a particular product (cert/id) is beta or not.

Comment 2 Carter Kozak 2014-01-03 16:33:35 UTC

This was fixed by using a different product id for beta.