Bug 1058764
| Summary: | Not possible to power off VM that failed migration. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Arik <ahadas> |
| Status: | CLOSED ERRATA | QA Contact: | Ilanit Stein <istein> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | acathrow, adahms, gklein, iheim, lpeer, mavital, michal.skrivanek, ofrenkel, Rhev-m-bugs, sherold, yeylon, zdover |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | is34 | Doc Type: | Bug Fix |
| Doc Text: |
The process for confirming completion of migration has been revised to add a null check that ensures the destination VDS is valid. This makes it possible to shut down virtual machines source hosts even if migration fails.
|
Story Points: | --- |
| Clone Of: | 1048790 | Environment: | |
| Last Closed: | 2014-03-03 13:32:03 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: | 1048790 | ||
| Bug Blocks: | |||
|
Comment 1
Michal Skrivanek
2014-01-28 13:53:37 UTC
Verified on is34.
Have 3 rhel hosts.
- Run VM on host1.
- Have host 3 avail memory not sufficient to contain this VM.
- Migrate VM (to any host).
- VM starts to migrate to host2 (since host 3 memory is full)
- While migration is running, Kill qemu process on host2 by:
ps aux | grep qemu | grep -v grep | grep -v supervdsmServer | awk '{print $2}' | xargs -I^ kill -9 ^
- As a result: a. migration fail b. Trying another host (host 3) - which fail as well. VM stays running on host1.
- Power off the VM succeeded.
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-2014-0227.html |