Red Hat Bugzilla – Bug 967466
PRD35 - [RFE] Show live migration progress in the UI
Last modified: 2015-02-11 12:53:19 EST
One possible solution could be progress bar in Status column (currently 'Migration from' text) of migrated VM.
still needs a proper vdsm patch(posted by Francesco),then backend, REST and UI support
Only the vdsm part merged
the issues mentioned in the tests are fixed in http://gerrit.ovirt.org/#/c/29763/ (bz: 1114997).
I would maybe add one more negative case: while migrating, kill the machine on the source host. It should turn down and the progress bar should be cleared. Please note that this is also fixed in the mentioned patch.
Otherwise they are good.
(oVirt Engine Version: 3.5.0-0.0.master.20140804172041.git23b558e.el6)
A VM with OS type win7, not installed with OS, 16000 MB memory, migration took 18 sec, but progress bar didn't show ant progress, even if doing often tab refresh.
Retested it with a VM that it's migration took longer (43 sec in engine),
and for that VM progress bar did show a percentage growth.
VM mentioned in bug description & in the attached logs has a too short migration,
and thus the there is no progress seen in the progress bar.
Therefore, moving bug back to ON_QA
Verification for this bug should be by the TCMS cases attached.
Verified by running all attached tcms cases on rhevm-3.5, vt2.2
Description of original problem:
VDSM should report migration progress to RHEVM in order to be able to control parameters such as migration time out , or to reach other logical decisions.
For example: If VM fails to migrate after 300 seconds and it succeeds to migrate 80 percent of the data , RHEVM can try again with bigger timeout.
For this kind of decisions VDSM should report migration process to RHEVM ( every x seconds or at migration process end time )
2 clones of the same BZ should be opened to VDSM and libvirt
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.