Description of problem:
In 2 v2v migration of 20 VMs/100GB disk, such error are displayed in evm.log:
[----] E, [2019-07-21T12:24:25.696326 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) MIQ(MiqQueue#deliver) Message id: , Error: [start is not permitted at state running]
[----] E, [2019-07-21T12:24:25.696555 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) [RuntimeError]: start is not permitted at state running Method:[block (2 levels) in <class:LogProxy>]
[----] E, [2019-07-21T12:24:25.696754 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) /var/www/miq/vmdb/app/models/job/state_machine.rb:36:in `signal'
In the first migration run - all VMs were migrated successfully,
and these messages appeared at the beginning of the migration.
In the second migration run, migration was cancelled for 2 VMs,
and the other 18 VMs migration started, shortly after the second migration round started, those errors started.
Version-Release number of selected component (if applicable):
Such errors messages should not appear. At least not as ERRORs.
Though it seem these errors are not failing the VMs migration,
they should not appear as ERRORs in the evm.log.
Maybe turn them into WARNINGs or DEBUG, or find another solution.
Created attachment 1592547 [details]
First migration run. Errors appear @ July 21 2019 8:03
Second migration run. Errors appear @ July 21 2019 12:24
Created attachment 1592548 [details]