Bug 1199670

Summary: Temporary pool validity incorrect
Product: Red Hat Enterprise Linux 6 Reporter: Sharath Dwaral <fsharath>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED NOTABUG QA Contact: John Sefler <jsefler>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: dgoodwin, jgalipea
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-13 14:03:15 UTC Type: Bug
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: 1125249    
Attachments:
Description Flags
Temporary pool validity none

Description Sharath Dwaral 2015-03-06 23:26:19 UTC
Created attachment 999026 [details]
Temporary pool validity

Description of problem:
Temporary pool validity incorrec

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.git.84.66aafd7.el6
python-rhsm: 1.14.2-1.git.0.fafb02d.el6

How reproducible:
Always

Steps to Reproduce:
1. subscribe to temporary pool
2. open GUI and in MY Subscription Tab click subscription
3. see attachment

Actual results:
The validity currently is 48hrs

Expected results:
Validity should be 24hrs it

Additional info:

Comment 2 John Sefler 2015-03-09 16:49:45 UTC
Here is an explanation for why the Start-End Date: is 03/05/2015-03/07/2015 when Sharath expected it should show 03/06/2015-03/07/2015....

1. The value shown for the end date of the unmapped_guests_only entitlement should be 24 hours from time the consumer *registered* (not subscribed).

2. The value shown for the start date of the unmapped_guests_only entitlement will actually come from the start date of the parent pool (which could have been established on a running candlepin several days ago).  In Sharath's case, his candlepin server was actually deployed and populated with pools on 03/05/2015.

Based these two reasons, I believe this is not a bug.  However, it may be less confusing and more accurate to make the start date of the unmapped_guests_only entitlement begin on the same date as the registered consumer's Validity Not Before date.

Comment 3 Devan Goodwin 2015-03-13 14:03:15 UTC
Closing NOTABUG after comments from John and Sharath.