Bug 1339612 - Vmdb Last Start Time bad date
Summary: Vmdb Last Start Time bad date
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.9.0
Assignee: Yuri Rudman
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ui:database
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 12:50 UTC by Matouš Mojžíš
Modified: 2018-03-01 13:06 UTC (History)
9 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:06:56 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Bad date shown (174.91 KB, image/png)
2016-05-25 12:50 UTC, Matouš Mojžíš 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Matouš Mojžíš 2016-05-25 12:50:11 UTC 
Created attachment 1161405 [details]
Bad date shown

Description of problem:
In VMDB summary is bad date for Last Start Time.
Time is okay, but date is wrong.

Version-Release number of selected component (if applicable):
5.5.4.2

How reproducible:
Always

Steps to Reproduce:
1. Go to Configure -> Database tab
2.
3.

Actual results:
Sat Jan 01 12:31:22 UTC 2000 

Expected results:
Wed May 25 12:31:22 UTC 2016 

Additional info:
Screenshot attached
Comment 2 Harpreet Kataria 2016-05-25 15:06:59 UTC 
UI is calling last_start_time method on VmdbDatabase record
https://github.com/ManageIQ/manageiq/blob/master/app/helpers/ops_helper/textual_summary.rb#L61
Comment 4 Yuri Rudman 2017-06-28 18:30:50 UTC 
PR: https://github.com/ManageIQ/manageiq/pull/15467
Comment 5 Matouš Mojžíš 2017-10-30 18:33:42 UTC 
Verified in 5.9.0.4. Last start time is now correct.
Comment 8 errata-xmlrpc 2018-03-01 13:06:56 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.

https://access.redhat.com/errata/RHSA-2018:0380
Note You need to log in before you can comment on or make changes to this bug.