tested on rhevm-3.4.1-0.23.el6ev.noarch.
Checked the following flows: MigrateVm', 'MigrateVmToServer', 'InternalMigrateVm', 'RunVm', 'RunVmOnc'.
in all flows except InternalMigrateVm, the job status is updated on job table. when starting the job, status=START. then I stop engine before the job is complete, then start engine. in job table the job is deleted.
as forInternalMigrateVm: this task's status is updated in step table and same flow I used for other jobs had resulted with MIGRATE_VM status UNKNOWN after engine restart.
retargeting to 3.4.2 as it's a corner case, not a critical problem
what?why? no way - this is still assigned!:)
not in scope for 3.4.2 (not included in 3.4.2 tracker -[RHEV] 3.4.2 Bug tracker - https://bugzilla.redhat.com/show_bug.cgi?id=1123858).
moving to 3.4.3
tested on rhevm-3.4.3-1.1.el6ev.noarch
1. updated FailedJobCleanupTimeInMinutes and JobCleanupRateInMinutes in vdc_options
2. Checked the following flows: MigrateVm', 'MigrateVmToServer', 'InternalMigrateVm', 'RunVm', 'RunVmOnc'.
in each case I invoked the action to start and restarted the engine before action could finish properly.
in all cases the job (or step in case of InternalMigrateVm) had status STARTED (which can be seen in DB) at the beginning.
upon engine restart the job/step was deleted from DB.
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.