RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

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.

Closing NOTABUG after comments from John and Sharath.