Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1478880

Summary:	creation date in templates disks subtab is in wrong format
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	Frontend.WebAdmin	Assignee:	shani <sleviim>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	amureini, bugs, ratamir
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:03:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lucie Leistnerova 2017-08-07 12:32:53 UTC

Description of problem:
Disk creation date in template is in different format than other dates.
Normally: Mar 16, 2017, 10:52:29 AM
In disks: 8/7/17

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170806164941.git514c1c9.el7.centos.noarch

How reproducible: always


Steps to Reproduce:
1. create some template with disk
2. go to Templates, select the one created and go to Disks subtab
3. see Creation Date

Actual results: date is in wrong format


Expected results: date is in the same format e.g. like templates Creation date


Additional info: 
The same problem is in templates Storage subtab by expanding storage.
In snapshots Disks subtab is the date format alright.

Comment 1 Raz Tamir 2017-08-27 08:25:53 UTC

Verified on ovirt-engine-4.2.0-0.0.master.20170826130128.git27024d1.el7.centos

The 'creation date' is - Aug 24, 2017, 5:20:17 PM

Comment 2 Sandro Bonazzola 2017-12-20 11:03:37 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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