Bug 1339612

Summary: Vmdb Last Start Time bad date
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: ApplianceAssignee: Yuri Rudman <yrudman>
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: low Docs Contact:
Priority: low    
Version: 5.5.0CC: abellott, cpelland, gtanzill, hkataria, jhardy, mpovolny, obarenbo, simaishi, yrudman
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:database
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:06:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Bad date shown none

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