Description of problem: Version-Release number of selected component (if applicable): # subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.45-1 subscription management rules: 5.14 subscription-manager: 1.14.1-1.el6 python-rhsm: 1.14.1-1.el6 How reproducible: always Steps to Reproduce: 1.client Registered time was "registered time is : 2015-03-05 18:29:06.845+05:30 " 2.# date Fri Mar 6 18:29:25 IST 2015 --> current time 3.#consumed list # subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Awesome OS with up to 4 virtual guests Provides: Awesome OS Server Bits SKU: awesomeos-virt-4 Contract: 2 Account: 12331131231 Serial: 5873392590627193143 Pool ID: ff8080814be9bfc9014be9c058321096 Provides Management: No Active: False Quantity Used: 1 Service Level: Service Type: Status Details: Subscription is expired --> subscription Expired Subscription Type: Multi-Entitleable Starts: 03/05/2015 Ends: 03/06/2015 System Type: Virtual 4.observed that still the product status is "partially subscribed" [root@dhcp35-114 ~]# subscription-manager list --installed +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Awesome OS Server Bits Product ID: 37060 Version: 6.1 Arch: ALL Status: Partially Subscribed ====> was expecting it to be set to "Expired" Status Details: Guest has not been reported on any host and is using a temporary unmapped guest subscription. Starts: 03/05/2015 Ends: 03/04/2016 # subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Insufficient Awesome OS Server Bits: - Guest has not been reported on any host and is using a temporary unmapped guest subscription. Actual results: Observed that still the product status is "partially subscribed" Expected results: After the 24hr subscription is expired, the status of the product should be set to "Expired" Additional info:
The validity of the temporary entitlements is not enforced by Candlepin but instead enforced by the certificate dates. The expired entitlement can exist on the server for up to 12 hours before it is erased. I would consider this issue to be working as designed so long as the entitlement disappears after 12 hours. The issue is that Candlepin doesn't have a ticking clock that will remove entitlements as soon as they expire. Instead we rely on jobs that run periodically to remove them. Please let me know if the expired entitlement does not disappear after 12 hours.
(In reply to Alex Wood from comment #1) > The validity of the temporary entitlements is not enforced by Candlepin but > instead enforced by the certificate dates. The expired entitlement can > exist on the server for up to 12 hours before it is erased. I would > consider this issue to be working as designed so long as the entitlement > disappears after 12 hours. The issue is that Candlepin doesn't have a > ticking clock that will remove entitlements as soon as they expire. Instead > we rely on jobs that run periodically to remove them. > > Please let me know if the expired entitlement does not disappear after 12 > hours. Yes, the Expired cert was removed. But my observation was related to product status not being changed to "Expired" after the 24hr pool was expired. As we discussed over IRC , may be its related to End date mismatch in the product list is's causing this Starts: 03/05/2015 Ends: 03/04/2016 I am clearing the needinfo request. Please re-check and let me know if more details needed
master commit 784ddf0be931e5a138f26905cd253bd92321abda
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Moving to closed per the updated candlepin process for bugs that have been merged or have been taken care of.