Red Hat Bugzilla – Bug 699442
Incorrect end date displayed in the subscription manager
Last modified: 2011-12-06 12:13:41 EST
Author: Adrian Likins <email@example.com>
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
Created attachment 497355 [details]
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.
Local time for the screenshot in comment 4 is: 05/06/2011 09:31 AM EST
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.
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
Created attachment 515779 [details]
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
moving to VERIFIED.
*** Bug 703286 has been marked as a duplicate of this bug. ***
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.