Bug 1033153
Summary: | DestroyVDSCommand called after CancelMigrateVDSCommand failure when attempting to cancel multiple live migrations at a time | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | vdsm | Assignee: | Vinzenz Feenstra [evilissimo] <vfeenstr> |
Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.2.0 | CC: | acathrow, bazulay, cboyle, flo_bugzilla, hateya, hchiramm, iheim, jentrena, juzhang, lpeer, lyarwood, mavital, michal.skrivanek, pnovotny, pstehlik, rgolan, Rhev-m-bugs, sherold, srevivo, vfeenstr, yeylon |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | 3.2.5 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
After attempting to cancel multiple live migrations, some virtual machines were killed. To fix this, when the migration is cancelled, libvirt raises an error to prevent the operation from proceeding, which also avoids calling the destination VDSM to create the virtual machine instance.
|
Story Points: | --- |
Clone Of: | 1023131 | Environment: | |
Last Closed: | 2013-12-18 13:58:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1023131 | ||
Bug Blocks: |
Comment 3
Charlie
2013-11-29 04:59:37 UTC
Verified in sf22: rhevm-3.2.5-0.48.el6ev.noarch vdsm-4.13.0-0.10.beta1.el6ev.x86_64 libvirt-0.10.2-29.el6.1.x86_64 Verified according to original bug 1023131, comment 0: 1. Crete 5 VMs, run them all and wait until they're up. 2. Select all of them and start to migrate them. 3. Wait for webadmin portal to display the hourglass for each guest. 3. Click on Cancel Migration. Result: All initiated migrations are cancelled and VMs are still running on the "source" host. Re-verifying after realizing that one of my hosts was running newer VDSM from 3.3 RHEVM (vdsm-4.13.0-0.10.beta1.el6ev.x86_64) and not the 3.2.5 one. Re-verified in sf22: RHEVM: rhevm-3.2.5-0.48.el6ev.noarch both hosts: vdsm-4.10.2-28.0.el6ev.x86_64, libvirt-0.10.2-29.el6.1.x86_64 Verification steps were the same as in comment 4, as well as were the results. 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. http://rhn.redhat.com/errata/RHBA-2013-1832.html |