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.
Bug 699442 - Incorrect end date displayed in the subscription manager
Summary: Incorrect end date displayed in the subscription manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: John Sefler
URL:
Whiteboard:
: 703286 (view as bug list)
Depends On: 695234
Blocks: rhsm-rhel62 702030
TreeView+ depends on / blocked
 
Reported: 2011-04-25 16:31 UTC by Adrian Likins
Modified: 2011-12-06 17:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 695234
Environment:
Last Closed: 2011-12-06 17:13:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
dates (340.84 KB, image/png)
2011-05-06 13:39 UTC, J.C. Molet
no flags Details
validuntil (76.71 KB, image/png)
2011-07-28 18:12 UTC, J.C. Molet
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1695 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2011-12-06 01:23:29 UTC

Comment 2 Adrian Likins 2011-04-25 21:22:55 UTC
commit 002129264af09a202d784de7c8d4f5f3d81bf39d
Author: Adrian Likins <alikins>
Date:   Mon Apr 18 14:16:43 2011 -0400

    699442: dates are being displayed incorrectly everywhere
    
    installed tab was storing a formatted date string, which
    was getting coverted to a datetime, losing it's timezone, and
    was then getting displayed incorrectly.
    
    Change all of our TreeStores to store datetime objects for
    dates instead of formatted strings, and make CellRendererDate
    do the formatting.
    
    Add parseDate to managerlib and make formatDate just format.
    parseDate expects an iso8601 style date and returns a datetime,
    while formatDate expects a datetime and returns a formatted
    string. Move LocalTz tzinfo subclass here from gui/utils.
    
    Note: for installedtab, we also changed the start/end dates
    displayed from being the _order_ start and end dates, to
    being the stand/end dates for the certificate.
    
    Try to be a little more consistent in our usage of formatDate vs strftime

Comment 4 J.C. Molet 2011-05-06 13:39:34 UTC
Created attachment 497355 [details]
dates

This seems to be working for the in all cases with the exception of the "Certificate Status" date given (see screenshot).  That one seems to be two days off from the actual date.

Comment 5 J.C. Molet 2011-05-06 13:49:41 UTC
Local time for the screenshot in comment 4 is:  05/06/2011 09:31 AM EST

Comment 6 Adrian Likins 2011-05-06 15:27:26 UTC
Argh. Indeed it is. Looks like a merge error since it's works in master, and there is a one liner that didn't make it from master to rhel6 that fixes it. 

Got a patch out for review.

Comment 8 John Sefler 2011-05-10 19:50:59 UTC
this bug should be used to verify the fix in the rhel62 release

Note: corresponding bug 702030 was used to verify fix in rhel6.1z
Note: corresponding bug 695234 was used to verify fix in rhel5.7

Comment 10 J.C. Molet 2011-07-28 18:12:31 UTC
Created attachment 515779 [details]
validuntil

new wording makes all the dates make sense.

screenshot dates match the cli and the cert:

[root@jmolet-vm0 entitlement]# subscription-manager list --consumed
+-------------------------------------------+
    Consumed Product Subscriptions
+-------------------------------------------+


ProductName:        	Awesome OS Server Bits   
ContractNumber:     	65                       
AccountNumber:      	12331131231              
SerialNumber:       	2001266316829453850      
Active:             	True                     
QuantityUsed:       	1                        
Begins:             	07/27/2011               
Expires:            	07/26/2012

Comment 11 J.C. Molet 2011-07-28 18:13:14 UTC
moving to VERIFIED.


subscription-manager-gnome-0.96.4-1.git.66.43ed963.el6.x86_64
subscription-manager-0.96.4-1.git.66.43ed963.el6.x86_64
subscription-manager-firstboot-0.96.4-1.git.66.43ed963.el6.x86_64
python-rhsm-0.96.7-1.git.4.ae2c338.el6.noarch

Comment 12 J.C. Molet 2011-08-08 12:50:39 UTC
*** Bug 703286 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2011-12-06 17:13:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1695.html


Note You need to log in before you can comment on or make changes to this bug.