Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): 5.6.1.2 and upstream How reproducible:each time Steps to Reproduce: 1. turn off auto-approval (or request more than 2 VMs on default setup) 2. create request to provision instance and set up schedule date/time (e.g. 18:00 or any other except 00:00) - submit 3. open request editing - check time - time is set to 00:00 expected result: time value remains the same actual result: time value is reset to 00:00 Additional info: such request will start provisioning if after editing request fits auto-approval without waiting for a time you set up during creating request Workaround: check schedule time each time you edit and set it up properly.
Drew - This might end up being a UI issue but first we should verify if the schedule date is making it into the options hash of the request. Lucy can help here if needed.
https://github.com/ManageIQ/manageiq-ui-classic/pull/1309
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/5bf141099e51ceaa5539646f8c2c6e95482ff10a commit 5bf141099e51ceaa5539646f8c2c6e95482ff10a Author: Lucy Fu <lufu> AuthorDate: Mon May 8 15:50:54 2017 -0400 Commit: Lucy Fu <lufu> CommitDate: Mon May 8 15:51:11 2017 -0400 Fix the issue with schedule time which was reset when editing provisioning request. It is called req_id instead of id in params hash with existing request. https://bugzilla.redhat.com/show_bug.cgi?id=1374005 app/controllers/application_controller/miq_request_methods.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)