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:
https://github.com/ManageIQ/manageiq-ui-classic/pull/2250
Verified on 5.9.0.11.
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