Bug 1422422 – [RFE] Allow for retirement based on date and time or delay

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

Bug 1422422 - [RFE] Allow for retirement based on date and time or delay

Summary:	[RFE] Allow for retirement based on date and time or delay

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	UI - OPS (Show other bugs)
Sub Component:
Version:	5.7.0
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	GA
Target Release:	5.9.0
Assigned To:	Milan Zázrivec
QA Contact:	Tasos Papaioannou
Docs Contact:

URL:
Whiteboard:	retirement
Keywords:	FutureFeature, PrioBumpQA, RFE

Depends On:
Blocks:	1480786 1523471
	Show dependency tree / graph

Reported:	2017-02-15 05:14 EST by Fabien Dupont
Modified:	2018-04-11 14:28 EDT (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:09:52 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	Feature
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	https://github.com/ManageIQ/manageiq/issues/13925	None	None	None	2017-02-15 05:14 EST
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 Fabien Dupont 2017-02-15 05:14:44 EST

Description of problem:
When setting future retirement on service or VM, the effective retirement happens on the specified date at 00:00 GMT. This behaviour is a bit limited and would gain being extended to handle delays or date and time.

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


How reproducible: Always


Steps to Reproduce:
1. On a service or VM, click on Lifecycle > Set retirement date
2. Specify a date in the date picker and save

Actual results:
The service or VM is retired on the specified date at 00:00 GMT.

Expected results:
It would be great to have more options than a date :
  - A delay to say, "I want my service/VM to be retired in X/Y minutes/hours/days/months"
  - A date and time to say "I want my service/VM to be retired on XX/YY/ZZZZ at AA:BB TZ"

This would allow for a more fine grained behaviour suiting the user needs.

The documentation should also mention that the retirement date means the VM will be retired at 00:00 GMT. In Europe it doesn't have a big impact, but in NA or APAC regions it can be confusing.

Additional info:

Comment 4 Milan Zázrivec 2017-09-27 14:22:39 EDT

https://github.com/ManageIQ/manageiq-ui-classic/pull/2250

Comment 5 Tasos Papaioannou 2017-11-28 10:16:13 EST

Verified on 5.9.0.11.

Comment 8 errata-xmlrpc 2018-03-01 08:09:52 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.