Bug 1627758

Summary:	[RFE] Expose time zone when setting retirement date and time and make it configurable
Product:	Red Hat CloudForms Management Engine	Reporter:	Jan Zmeskal <jzmeskal>
Component:	UI - OPS	Assignee:	Harpreet Kataria <hkataria>
Status:	CLOSED WONTFIX	QA Contact:	Jad Haj Yahya <jhajyahy>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.10.0	CC:	dmetzger, hkataria, lavenel, mpovolny, obarenbo
Target Milestone:	GA	Keywords:	AutomationBlocker, FutureFeature
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-18 14:32:49 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:

Description Jan Zmeskal 2018-09-11 12:03:33 UTC

Description of problem:
When setting retirement date for a VM, it looks like it's displayed on Screenshot 1. What's the problem with that? The datepicker assumes that you provide date & time in your local time zone (that information is acquired from browser). It might be completely different time zone than the one specified
- In appliance Configuration
- On appliance virtual machine

When you save the retirement date for your VM, it gets converted from your local time zone to UTC and displayed in flash message as displayed on Screenshot 2.

Now the essence of the problem is this: User has no way how to know that the datepicker displays time & date in their current time zone. This information is not displayed anywhere and it's far from obvious.
Also, they don't have a way how to change that and that might be problem as well. If you are a CFME operator and take care about infrastructure in different parts of world, you probably don't want to operate in your current time zone, but in UTC or some other standard time zone for your company.

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

How reproducible:
100 %

Steps to Reproduce:
1. Have a CFME appliance with infra provider.
2. Provision a VM on that provider.
3. Go to your VM's detail page, click Lifecycle -> Set Retirement Date and try to pick Specific Date and Time.

Actual results:
The time zone of the datepicker is neither exposed, nor configurable.

Expected results:
See Description.

Additional info:
I originally reported this as a bug, but was asked to file a RFE. More background information is available in my original bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1626971

Comment 4 Jan Zmeskal 2018-10-02 14:07:50 UTC

Can I please request backport of this RFE to all CFME major versions that are under current development? Since UI timezone during setting of retirement date is being determined by browser timezone, it's no longer possible to create deterministic automated UI tests for retirement functionality. 

Since CFME QAs are distributed around the whole world, we need to have a way how to unambiguously set the timezone we are working with during setting retirement.