Bug 967855 - engine: unlock_entity is not locating locked snapshots
Summary: engine: unlock_entity is not locating locked snapshots
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.1.5
Assignee: Eli Mesika
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
: 958341 (view as bug list)
Depends On: 958370
Blocks: 902971 948448
TreeView+ depends on / blocked
 
Reported: 2013-05-28 12:30 UTC by Idith Tal-Kohen
Modified: 2018-12-02 17:28 UTC (History)
18 users (show)

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.
Clone Of: 958370
Environment:
Last Closed: 2013-06-18 09:35:20 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0950 0 normal SHIPPED_LIVE rhevm 3.1.5 bug fix update 2013-06-18 13:34:15 UTC
oVirt gerrit 14494 0 None None None Never
oVirt gerrit 14530 0 None None None Never

Comment 1 Barak 2013-06-03 13:00:34 UTC 
*** Bug 958341 has been marked as a duplicate of this bug. ***
Comment 3 Aharon Canan 2013-06-10 15:41:24 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"
Comment 6 errata-xmlrpc 2013-06-18 09:35:20 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-0950.html
Note You need to log in before you can comment on or make changes to this bug.