Bug 1285232 - [RFE] subscription-manager should be limited to activation keys by default even if other product certs are available on host
Summary: [RFE] subscription-manager should be limited to activation keys by default ev...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.1.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 260381
TreeView+ depends on / blocked
 
Reported: 2015-11-25 09:25 UTC by Komal
Modified: 2019-09-12 09:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-08 12:04:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Komal 2015-11-25 09:29:08 UTC
Hello,

Looking for enhancement in following behavior observed on host registered to satellite 6 via activation key.

When registering a host with an activation key we choose which products we would like to license with that activation key. However, if additional products are added to the host rhsmcertd will pull entitlements from all available rather than limiting scope to the activation key.

As of now to workaround this issue cu manually need to remove the extra product certs from host system under /etc/pki/product directory as auto attach pulls all subscriptions matching available product.

Can this be automated and fixed in satellite 6.1.4 so as to consume subscription only from corresponding activation key.

Regards,
Komal

Comment 3 Bryan Kearney 2015-12-10 22:01:14 UTC
Clearing flags to make sure it gets triaged.

Comment 4 Mike McCune 2015-12-17 16:53:15 UTC
Why not turn off the auto flag on the activation key and specify the subscriptions manually on the activation key?

This should limit what subscriptions the hosts consume and not have things change when rhsmcertd runs.

Comment 8 Bryan Kearney 2016-07-26 19:09:42 UTC
Moving 6.2 bugs out to sat-backlog.


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