Bug 1343935

Summary:	[RFE] User specified rules for auto-attach
Product:	[Community] Candlepin	Reporter:	Beat Rubischon <brubisch>
Component:	candlepin	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	bcourt, candlepin-bugs, egolov, jentrena, klaas, ktordeur, mschibli, mstead, mtessun, patalber, redakkan, rjerrido, sreber
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-08 09:58:17 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:	1422844

Description Beat Rubischon 2016-06-08 11:08:56 UTC

Description of problem:

"subscription-manager auto-attach" takes the "first" available entitlement offering the required RHEL subscription. I saw a Datacenter Subscription on a standalone system (SFDC 01627925, account 818035), which confused the customer.

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

subscription-manager-1.15.9-15.el7.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Choose an account with a large amount of different entitlements
2. Run subscription-manager auto-attach

Actual results:

A random entitlement is taken.

Expected results:

A useful subscription attached.

Additional info:

From Red Hat point ov view, the most expensive entitlement should be applied (I think about RHEL Premium, RHEL Standard, Developer subscriptions).

From Customer point of view, the least expensive entitlement should be applied.

Datacenter entitlements or products with included RHEL subscriptions (OpenShift, OpenStack, Satellite, ...) should never be applied automatically.

Comment 7 Klaas Demter 2018-11-26 10:46:17 UTC

is syspurpose in rhel 8 a first step towards the goal of this bz?

https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#syspurpose

Comment 8 Rich Jerrido 2018-11-26 12:18:47 UTC

(In reply to Klaas Demter from comment #7)
> is syspurpose in rhel 8 a first step towards the goal of this bz?
> 
> https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#syspurpose

Sort of. As RHEL8 doesn't have variants (Server/Workstation/ComputeNode), we needed a means to allow the user to describe the usage of the system. 

That data (the system purpose) is fed to the subscription tools (sub-man/Candlepin) as will be used as a heuristic to better attach subscriptions. 

If (when?) we chose to implement truly user-specified rules (see also bz1401106), syspurpose would be one of the many parameters the user can use.

Comment 12 Rich Jerrido 2022-04-08 09:58:17 UTC

With the advent of Simple Content Access (https://access.redhat.com/articles/simple-content-access), this feature is rendered obsolete.

Comment 13 Red Hat Bugzilla 2023-09-14 23:59:40 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days