Bug 949690
| Summary: | vdsm: can't remove/export a vm with exception on getAllVolumes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Idith Tal-Kohen <italkohe> |
| Component: | vdsm | Assignee: | Eduardo Warszawski <ewarszaw> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel Paikov <dpaikov> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.2.0 | CC: | abaron, amureini, bazulay, cpelland, dron, hateya, iheim, lpeer, lyarwood, scohen, sgrinber, ykaul, zdover |
| Target Milestone: | --- | Keywords: | Regression, ZStream |
| Target Release: | 3.1.4 | Flags: | amureini:
Triaged+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, VDSM was unable to export or remove virtual machines in certain cases, especially when orphaned images were present in the storage domain and those orphaned images had been added to the storage domain during live storage migration tests. This meant that in certain cases, you would be unable to remove virtual machines.
A patch to VDSM which allows storage domains to be uncoupled from orphaned images. It is now possible to export and remove virtual machines, even if those virtual machines are associated with orphaned images.
|
Story Points: | --- |
| Clone Of: | 917363 | Environment: | |
| Last Closed: | 2013-05-01 18:25:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 917363 | ||
| Bug Blocks: | |||
|
Comment 5
Daniel Paikov
2013-04-23 07:28:07 UTC
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-0774.html |