Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 912698

Summary: Multi-entitlement not supported for pool - 1 entitlement applied to activation key
Product: [Retired] Subscription Asset Manager Reporter: Matthew Gyurgyik <matthew>
Component: candlepinAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: sthirugn <sthirugn>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: bkearney, inecas, lzap, mmccune, omaciel
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 11:06:22 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:
Attachments:
Description Flags
Screenshot of infra-2 activation key none

Description Matthew Gyurgyik 2013-02-19 13:01:43 UTC
Created attachment 699431 [details]
Screenshot of infra-2 activation key

Description of problem:
When attempting to register a system via an activation key subscription manager shows "Multi-entitlement not supported for pool with id 'xxxxxxxxxxxxx'."

System in question has two sockets.

How reproducible: Always

Step to reproduce:
1. Create activation key with one subscription added to it.
2. Register against system with two sockets  

Actual results:
Multi-entitlement not supported for pool with id 'xxxxxxxxxxxxx'.

Expected results:
Successful registration and subscription consumption.

Additional info:
# subscription-manager register --autosubscribe --org MYORG --activationkey infra-2
Multi-entitlement not supported for pool with id 'xxxxxxxxxxxxx'.

Comment 1 Ivan Necas 2013-02-19 13:48:30 UTC
Additional info: manual subscription (without ak) works fine

Comment 2 Ivan Necas 2013-02-19 14:34:51 UTC
I was not able to reproduce on latest katello nightly. Going to checking SAM-1.1 directly.

Comment 3 Og Maciel 2013-02-19 14:39:52 UTC
This may be related to candlepin's cert v3... SAM 1.1 does not turn this on.

Comment 5 Ivan Necas 2013-02-20 08:59:45 UTC
There seems to be an inconsistency in activation key algorithm and the manifest. I've contacted customer portal team for help here.

Comment 8 Ivan Necas 2013-02-21 14:36:04 UTC
After more investigation here is more detailed error description: when the activation key was subscribing the machine, it didn't take the number of sockets per pool into account, therefore, for subscription such as "Red Hat Enterprise Linux Server (1-2 sockets)" a machine with 2 sockets was tried to consume quantity of 2 instead of 1.

I'm sending fix for this issue later today.

Comment 9 Ivan Necas 2013-02-21 15:09:31 UTC
The fix proposed here:

https://github.com/Katello/katello/pull/1633

Comment 13 Ivan Necas 2013-03-06 15:09:07 UTC
Merged

Comment 14 sthirugn@redhat.com 2013-09-24 16:44:22 UTC
Verified.

1. Created activation key with 2 subscriptions (The subscriptions is an Instance based, stackable, Limits: 2 sockets/subscription)
2. Register a client with 6 sockets using activation key
Result: Successful registration and Partial Compliance
Details - 
Red Hat Enterprise Linux Server, Premium 	Only covers 2 of 6 sockets. 
2. Register a client with 4 sockets using activation key
Result: Successful registered and fully Compliant
3. Register a client with 4 sockets using activation key
Result: Successful registered and fully Compliant

Version Tested:
* candlepin-0.8.26-1.el6sam.noarch
* candlepin-cert-consumer-cloud-qe-19.idm.lab.bos.redhat.com-1.0-1.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.8.26-1.el6sam.noarch
* candlepin-tomcat6-0.8.26-1.el6sam.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-2.el6sat.noarch
* katello-cli-1.4.3-11.el6sat.noarch
* katello-cli-common-1.4.3-11.el6sat.noarch
* katello-common-1.4.3-15.el6sam_splice.noarch
* katello-configure-1.4.4-4.el6sat.noarch
* katello-glue-candlepin-1.4.3-15.el6sam_splice.noarch
* katello-glue-elasticsearch-1.4.3-15.el6sam_splice.noarch
* katello-headpin-1.4.3-15.el6sam_splice.noarch
* katello-headpin-all-1.4.3-15.el6sam_splice.noarch
* katello-selinux-1.4.4-2.el6sat.noarch
* thumbslug-0.0.34-1.el6sam.noarch
* thumbslug-selinux-0.0.34-1.el6sam.noarch

Comment 15 sthirugn@redhat.com 2013-09-24 17:09:50 UTC
Error on my verification steps above.  This is the updated one:

Verified.

1. Created activation key with 2 subscriptions (The subscriptions is an Instance based, stackable, Limits: 2 sockets/subscription)
2. Register a client with 6 sockets using activation key
Result: Successful registration and Partial Compliance
Details - 
Red Hat Enterprise Linux Server, Premium 	Only covers 2 of 6 sockets. 
3. Register a client with 4 sockets using activation key
Result: Successful registered and Partial Compliance
Details - 
Red Hat Enterprise Linux Server, Premium 	Only covers 2 of 4 sockets. 
4. Register a client with 2 sockets using activation key
Result: Successful registered and fully Compliant

Comment 17 errata-xmlrpc 2013-10-01 11:06:22 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.

http://rhn.redhat.com/errata/RHEA-2013-1390.html