Bug 891345
| Summary: | 3.1.z - [vdsm] lease files are not removed when removing volumes in file SDs v3 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | vdsm | Assignee: | Yeela Kaplan <ykaplan> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abaron, bazulay, cpelland, iheim, ilvovsky, lpeer, oourfali, ykaplan, ykaul, zdover |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 6.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | storage | ||
| Fixed In Version: | vdsm-4.10.2-1.1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, removing volumes from version 3 storage domains did not delete the corresponding lease files. Consequently, after the snapshot of a virtual machine was deleted, the virtual machine could not be removed. An update renames lease files on v3 storage domains when virtual machine data and metadata files are deleted, so a virtual machine can be successfully deleted after its snapshots are deleted.
|
Story Points: | --- |
| Clone Of: | 886842 | Environment: | |
| Last Closed: | 2013-02-25 19:07:33 UTC | Type: | Bug |
| 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: | 886842 | ||
| Bug Blocks: | 891343 | ||
|
Comment 1
Ayal Baron
2013-01-02 21:54:19 UTC
vdsm-4.10.2-1.2.el6.x86_64. tested according steps to reproduce. VM on file SD successfully deleted after snapshot creation and deletion. 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-0555.html |