Bug 1339612 – Vmdb Last Start Time bad date

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1339612 - Vmdb Last Start Time bad date

Summary:	Vmdb Last Start Time bad date

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Appliance (Show other bugs)
Sub Component:
Version:	5.5.0
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	GA
Target Release:	5.9.0
Assigned To:	Yuri Rudman
QA Contact:	Matouš Mojžíš
Docs Contact:

URL:
Whiteboard:	ui:database
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-25 08:50 EDT by Matouš Mojžíš
Modified:	2018-03-01 08:06 EST (History)
CC List:	9 users (show)

See Also:
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 08:06:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Bad date shown (174.91 KB, image/png) 2016-05-25 08:50 EDT, Matouš Mojžíš	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:0380	normal	SHIPPED_LIVE	Moderate: Red Hat CloudForms security, bug fix, and enhancement update	2018-03-01 13:37:12 EST

Groups: None (edit)

Description Matouš Mojžíš 2016-05-25 08:50:11 EDT

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 11:06:59 EDT

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 14:30:50 EDT

PR: https://github.com/ManageIQ/manageiq/pull/15467

Comment 5 Matouš Mojžíš 2017-10-30 14:33:42 EDT

Verified in 5.9.0.4. Last start time is now correct.

Comment 8 errata-xmlrpc 2018-03-01 08:06:56 EST

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.