Bug 750351

Summary:	expired subscriptions are still bound to the consumer
Product:	[Community] Candlepin	Reporter:	blittle
Component:	candlepin	Assignee:	Michael Stead <mstead>
Status:	CLOSED CURRENTRELEASE	QA Contact:	John Sefler <jsefler>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	0.5	CC:	acarter, aedwards, mstead, smunilla, sshevach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Solaris
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Since IT is triggering refresh pools off of expiry, the solution was to unbind expired subscriptions during refresh pools. Refresh pools will now remove any expired subscriptions, along with any of its associated pools, and will revoke consumer's entitlements from these pools.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-17 13:03:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	682238

Description blittle 2011-10-31 19:25:59 UTC

Description of problem:
expired subscriptions are still binded to the consumer

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:

Environment- https://rails-fte.gss.devlab.phx1.redhat.com/management/consumers/

login-rhn-cservice-acarter
pw-redhat

1. Created a rhui consumer.

2. Add a 60 day Supported Red Hat Update Infrastructure for Cloud Providers Evaluation subscription that expired on 10/28/11.

3. On 10/31/11, I noticed the 60 day Supported Red Hat Update Infrastructure for Cloud Providers Evaluation subscription was removed from the main subscription list.

4.  When I viewed the the rhui consumer list seven consumers still had the expired subscription displayed on the details page.  All the consumers have the name "cloud1".
  
Actual results:
Expired subscriptions display on consumer details page after expiration.

Expected results:
Expired subscriptions should be purged on the expiration date.

Additional info:

Comment 3 Michael Stead 2011-11-08 19:54:19 UTC

Not 100% sure what is being requested here.

Are we looking to have expired entitlements filtered? or be automatically revoked by candlepin?

Would marking them as expired on the web UI be another option? This seems like it could be useful.

Comment 4 Amanda Carter 2011-11-08 20:11:45 UTC

This bug is regarding subscriptions that are bound to a consumer, not the Available Subscription list. The subscription should no longer be bound to the consumer when it has passed its expiration date. 

Revocation should already be handled.

Comment 5 Michael Stead 2011-11-15 22:42:13 UTC

Fix submitted in:

master: ba62d784d2d3befb0a0d4f35b229bccead431696
0.4: 69de6445fe9e79f7be6783c884401ea3b6aeff29

See technical details.

Comment 6 Michael Stead 2011-11-15 22:42:13 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Since IT is triggering refresh pools off of expiry, the solution was to unbind expired subscriptions during refresh pools.

Refresh pools will now remove any expired subscriptions, along with any of its associated pools, and will revoke consumer's entitlements from these pools.

Comment 8 Bryan Kearney 2012-07-17 13:03:45 UTC

Marking all community bugs modified or beyong as closed.