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 497909 [details]
dates

Description of problem:
This is a partial clone of 699442, see https://bugzilla.redhat.com/show_bug.cgi?id=699442#c6

The certificate status is a couple of days off from the actual end date.

Steps to Reproduce:
1. Set up a box with subscription-manager-gui
2. Install one product in your /etc/pki/product
3. Subscribe to the pool that covers that product
4. Look at your compliance status (see screenshot)
  
Actual results:
The compliance status is a couple of days off.

Expected results:
The compliance status date has some connection to reality.

Altering this requires invasive changes that would likely create other bugs in the cert logic. Moving out to 6.2.

Is this still reproducible? I can't get it to happen here, and digging through the code everything looks to be in order. The compliance notice should display last cert end date + 1 day. Everything seems to be using GMT as far as I can tell, at least if the cert is specifying GMT. 

Tested with various timezones, jumping around to different hours around midnight, can't get it to do the above. My Subs tab still shows me July 31 in my case, and the compliance notice says "until" Aug 1.

I believe this was fixed in 699442, marking a duplicate.

*** This bug has been marked as a duplicate of bug 699442 ***