Description of problem: Candlepin will not autosubscribe to a pool with an unlimited quantity. Version-Release number of selected component (if applicable): How reproducible: Always NOTE: This has nothing to do with data center subscriptions, but using candlepin's data center test data is the easist way to reproduce. Steps to Reproduce: 1. Register host consumer and consume subscription "Awesome OS Server Basic (data center)" only. This will create a virtual pool with an unlimited quantity. This bonus pool will have an SLA of "Full-Service". 2. Run "sudo virt-who -d -o" to associte the guest. 3. Ensure that only the "37060.pem" product is installed on the guest. 4. Register a guest consumer in the subscription-manager GUI -- allow autosubscribe on register. 5. When the service level selector is displayed, notice that "Full-Service" is not listed, even though the pool would satisfy compliance. Actual results: When the service level selector is displayed, notice that "Full-Service" is not listed, even though the bonus pool would satisfy the system. Expected results: Full-Service SLA should be in the SLA list since the associated pool will cover the guest system. Selecting this SLA should show the bonus pool in the next dialog -- Awesome OS Server Basic (dc-virt) Additional info: This is because there is an error in how candlepin's rules are filtering pools when determining best_pools. A check for unlimited quantity was missing.
Pull Request submitted for review: https://github.com/candlepin/candlepin/pull/363
Fixed by commit https://github.com/candlepin/candlepin/commit/af01ac7a98ab24d589fda339d75a84552fad31ca Available in master branch, and will be available in candlepin-0.8.25-1
nm, seems i found an SKU to use (with unlimited guests and Premium support type).
# REOPEN doing UI registration of the virtual guest it (still) consumes the physical pool of the SKU. scenario: 1. generate manifest from "Red Hat Enterprise Linux Advanced Platform, Premium (unlimited sockets)" 2. import manifest to the SAM latest. 3. register and autosubscribe the host. 4. run virt-who (it reports the guests recently prepared) 5. configure the guest having Gnome there. 6. via RHSM GUI perform steps above (see screenshots attached). 7. result: the guest gets subscribed to the physical pool (but should be chosen the virt. pool instead). NOTE: cli registration with --autosubscribed works perfectly - virtual pool gets chosen. versions: RHSM packages: ==== subscription-manager-1.1.23-1.el6.x86_64 subscription-manager-gui-1.1.23-1.el6.x86_64 subscription-manager-firstboot-1.1.23-1.el6.x86_64 python-rhsm-1.1.8-1.el6.x86_64 ==== SAM 1.3 ==== candlepin-0.8.26-1.el6sam.noarch candlepin-cert-consumer-hephaestus.usersys.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 ruby193-rubygem-ldap_fluff-0.2.2-1.el6sat.noarch thumbslug-0.0.34-1.el6sam.noarch thumbslug-selinux-0.0.34-1.el6sam.noarch ==== (screenshots attaching now...)
Created attachment 802762 [details] step1
Created attachment 802764 [details] step2
Created attachment 802765 [details] step3
This should be fixed in the latest candlepin/sam.
Closing out old bugs. If you are still having an issue, please feel free to re-open.