Bug 967855
| Summary: | engine: unlock_entity is not locating locked snapshots | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Idith Tal-Kohen <italkohe> |
| Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.0 | CC: | acathrow, amureini, bazulay, cpelland, dron, dyasny, hateya, iheim, jbiddle, lnatapov, lpeer, mkalinin, pstehlik, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.1.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | infra | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, unlock_entity failed to find locked snapshots and unlock them even after the associated virtual machine and virtual disk were unlocked successfully.
Now, locked snapshots are appropriately unlocked along with their associated virtual machines and virtual disks.
|
Story Points: | --- |
| Clone Of: | 958370 | Environment: | |
| Last Closed: | 2013-06-18 09:35:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 958370 | ||
| Bug Blocks: | 902971, 948448 | ||
|
Comment 1
Barak
2013-06-03 13:00:34 UTC
verified using 3.1.5 (si29)
verification steps:
1. lock snapshots
a. enter the engine DB
b. run - "UPDATE snapshots SET status='LOCKED' where status='OK';"
2. check that snapshots are locked
("select snapshot_id,description,status from snapshots ;")
3. run - "./unlock_entity.sh -t snapshot -i <snapshot_id> -u engine"
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-0950.html |