Description of problem: Version-Release number of selected component (if applicable): subscription-manager version subscription management server: 0.9.23-1 subscription management rules: 5.11 subscription-manager: 1.12.12-1.el6 python-rhsm: 1.12.5-1.el6 How reproducible: 3/3 Steps to Reproduce: 1.List installed with insufficient subscriptions ------------------------------------------ # subscription-manager attach --pool ff80808147e82d4b0147e82e049a0b85 Successfully attached a subscription for: Awesome OS Stackable guest limit 4 [root@cisco-b200m1-03 ~]# subscription-manager list --installed +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Awesome Hypervisor Bits Product ID: 98121 Version: 6.1 Arch: ALL Status: Not Subscribed Status Details: Not supported by a valid subscription. Starts: Ends: Product Name: Awesome OS Server Bits Product ID: 37060 Version: 6.1 Arch: ALL Status: Partially Subscribed Status Details: Only supports 4 of 5 virtual guests. Starts: 08/17/2014 Ends: 08/17/2015 # subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Stackable guest limit 4 Provides: Awesome OS Server Bits SKU: awesomeos-guestlimit-4-stackable Contract: 3 Account: 12331131231 Serial: 434985099990184240 Pool ID: ff80808147e82d4b0147e82e049a0b85 Active: True Quantity Used: 1 Service Level: Service Type: Status Details: Only supports 4 of 5 virtual guests. Subscription Type: Stackable Starts: 08/17/2014 Ends: 08/17/2015 System Type: Physical 2.Enable auto-heal , restarted rhsmcertd services wait for 2mins 3. subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS Super Hypervisor Provides: Awesome Hypervisor Bits SKU: awesomeos-super-hypervisor Contract: 3 Account: 12331131231 Serial: 2565415080292980865 Pool ID: ff80808147e82d4b0147e82e04530b53 Active: True Quantity Used: 1 Service Level: Service Type: Status Details: Subscription Type: Stackable Starts: 08/17/2014 Ends: 08/17/2015 System Type: Physical Subscription Name: Awesome OS Server Basic Provides: Awesome OS Server Bits ---------------> this subscription is "NOT" actually needed as the above hypervisor subscription is capable of making the product compliant SKU: awesomeos-server-basic Contract: 2 Account: 12331131231 Serial: 5325822594991740620 Pool ID: ff80808147e82d4b0147e82e124a19f3 Active: True Quantity Used: 1 Service Level: None Service Type: Self-Support Status Details: Subscription Type: Standard Starts: 08/17/2014 Ends: 08/17/2015 System Type: Physical Subscription Name: Awesome OS Stackable guest limit 4 Provides: Awesome OS Server Bits SKU: awesomeos-guestlimit-4-stackable Contract: 3 Account: 12331131231 Serial: 434985099990184240 Pool ID: ff80808147e82d4b0147e82e049a0b85 Active: True Quantity Used: 1 Service Level: Service Type: Status Details: Subscription Type: Stackable Starts: 08/17/2014 Ends: 08/17/2015 System Type: Physical Actual results: Expected results: Additional info:
Actual results: subscription "Awesome OS Server Basic" is attached on the system, but the system is already healed by the "Awesome OS Super Hypervisor" (guest-limit =-1) subscription Expected results: subscription "Awesome OS Server Basic" is not actually needed on the system, as the "hypervisor" subscription is capable of making the product " Awesome OS Server Bits" compliant
I can see similar behavior. I will investigate further.
I confirm this is an issue. The auto-attach logic will always suggest only those pools which combined with already consumed subs will be compliant with the guest_limit. This means that in your case it will only suggest those that combined with awesomeos-guestlimit-4-stackable will be guest_limit compliant. Even though this seems like rather severe issue (I can think of several scenarios where current auto-attach fails completely), there is no easy fix for this so I will lower priority on this bug. In case this hits a customer, it is important that he firstly manually attaches some sub that will cover guest_limit. After that auto-attach will work fine.
Thank you for your interest in Candlepin. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the project, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to open a new bug with more up to date details. Thank you.