Description of problem: As of nightly build for miq on master.20180714230232_f07d954, new feature to schedule migration was added. I tried to perform a scheduled migration and it did not run at set time. Then I made sure appliance timezone is set to my local timezone EST and it would still not begin. Version-Release number of selected component (if applicable): master.20180714230232_f07d954 How reproducible: 100% Steps to Reproduce: 1.Add VMware and RHV Environments and configure conversion hosts 2.Create new infra mapping and create a migration plan without running it. i.e. save it for later. 3.Schedule it to run at a specific date and time. Wait for it to start running at that time. Actual results: It would not actually start executing even after scheduled time is past. Expected results: Scheduled migration should run at set time it is supposed to run. Additional info:
https://github.com/ManageIQ/miq_v2v_ui_plugin/issues/495
https://github.com/ManageIQ/manageiq/pull/17717
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/27c1dbdae8568dc33a6606413f83c82cbf08d864 commit 27c1dbdae8568dc33a6606413f83c82cbf08d864 Author: Brandon Dunne <brandondunne> AuthorDate: Tue Jul 17 11:06:19 2018 -0400 Commit: Brandon Dunne <brandondunne> CommitDate: Tue Jul 17 11:06:19 2018 -0400 Fix class name for queueing Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1601930 app/models/service_template.rb | 2 +- spec/models/service_template_spec.rb | 13 + 2 files changed, 14 insertions(+), 1 deletion(-)
on 5.10.0.6 I could see migration kicks-off at time I scheduled it to.