Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #837143 +++
Description of problem:
Auto-subscription using activation key fails with the error,
Multi-entitlement not supported for pool with id XXXXX
under the condition:
1. Activation Key contains only virtual type subscription.
2. RHEL guest VM to subscribe has multilple vCPUs.
Version-Release number of selected component (if applicable):
For SAM server:
# rpm -qa | grep -E "(katello|candlepin)"
katello-configure-0.3.7-1.el6_2.noarch
katello-cli-headpin-0.2.2-1.el6_2.noarch
candlepin-tomcat6-0.6.5-1.el6_2.noarch
katello-certs-tools-1.1.5-1.el6_2.noarch
katello-common-0.3.3-1.el6_2.noarch
katello-headpin-0.2.13-1.el6_2.noarch
katello-glue-candlepin-0.3.3-1.el6_2.noarch
katello-cli-common-0.3.5-2.el6_2.noarch
candlepin-0.6.5-1.el6_2.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-selinux-0.2.4-1.el6_2.noarch
katello-headpin-all-0.2.13-1.el6_2.noarch
For Guset VM:
# rpm -qa | grep subscription
subscription-manager-0.99.19.3-1.el6_3.x86_64
How reproducible:
1. Register and subscribe KVM host with physical type subscription.
2. Create activation key containing only virtual type subscription derived from the physical one.
3. Register KVM guest using the activation key.
Actual results:
If the guest VM has two vCPUs, subscription fails with the error:
Multi-entitlement not supported for pool with id XXXXX.
If the guest VM has one vCPU, it succeeds as expected.
I investigated the exceution path of this failed process.
1. Katello successfully POSTed the request to Candlepin with the following URI:
(POST /candlepin/consumers/c65be5db-0fae-4919-8c96-a72a1d93b36f/entitlements?pool=4028fa8b3846bd3e013847f0d3f402b8&quantity=2)
2. Then, Candlepin *possiblly* returns the exception "rulefailed.pool.does.not.support.multi-entitlement" at the following point of code.
./src/main/resources/rules/default-rules.js
564 if (pre.getQuantity() > 1 && product.getAttribute("multi-entitlement") != "yes") {
565 pre.addError("rulefailed.pool.does.not.support.multi-entitlement");
566 }
I guess either of them would be the root cause of the problem.
- The quantity attribute should not reflect the number of vCPUs?
- Candlepin should accept quantity>1 for non-muti-entitlement subscription?
--- Additional comment from enakai on 2012-07-03 08:52:34 EDT ---
I changed the component to Katello as it wouldn't be a Candlepin's problem.
It looks Katello always assumes that the number of subscription (quantity) should equal to the number of sockets when auto-subscribing with an activation key. But all subscriptions don't necessarily follow that rule.
Activation key needs to contain information not only for subscriptions but also for their consumption rules, right?
This bug was closed because of a lack of activity. If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.