Red Hat Bugzilla – Bug 1316632
The retirement date is off by a day when I retire an VM.
Last modified: 2017-08-21 09:09:11 EDT
Description of problem: I just set the retirement date on a VM to today. It retired the VM correctly, but when I look at the summary page for the VM, the date displayed is yesterday. Version-Release number of selected component (if applicable): 5.6 How reproducible: At least once. Steps to Reproduce: 1. Find a VM and LifeCycle-Set Retirement Date 2. Pick today from the date widget. 3. After retirement, check the date field for the retirement date. Actual results: Today is 03-10-2016 and the retirement date fields look like this. Retirement Date 03/09/16 Retirement state Retiring Expected results: Additional info: I checked the appliance system date: [root@10-16-7-137 ~]# date Thu Mar 10 11:13:50 EST 2016 [root@10-16-7-137 ~]#
Martin, Can you look into this one, it looks like inconsistency between Timezone, when i select date in calendar to today's date, it sends up date-1 in the transaction to server hence incorrect date is getting saved. Let me know if you need help recreating or have questions. Thanks, ~Harpreet
https://github.com/ManageIQ/manageiq/pull/11156
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/298963247759838bd9eeba5cd6ad25cd0620c7eb commit 298963247759838bd9eeba5cd6ad25cd0620c7eb Author: Martin Hradil <mhradil@redhat.com> AuthorDate: Fri Sep 9 16:46:38 2016 +0000 Commit: Martin Hradil <mhradil@redhat.com> CommitDate: Fri Sep 16 09:20:39 2016 +0000 Migrate retires_on and retirement_last_warn to datetime https://bugzilla.redhat.com/show_bug.cgi?id=1316632 .../20160912160750_change_retires_on_to_datetime.rb | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 db/migrate/20160912160750_change_retires_on_to_datetime.rb
https://github.com/ManageIQ/manageiq/pull/12530
*** Bug 1419150 has been marked as a duplicate of this bug. ***
https://github.com/ManageIQ/manageiq-ui-classic/pull/1368
This bug has been open for more than a year and is assigned to an older release of CloudForms. If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.