Bug 958341 - backport fix to unlock utility to work for snapshots
Summary: backport fix to unlock utility to work for snapshots
Keywords:
Status: CLOSED DUPLICATE of bug 967855
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks: 902971
TreeView+ depends on / blocked
 
Reported: 2013-05-01 01:35 UTC by Marina Kalinin
Modified: 2018-12-02 17:28 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-03 13:00:33 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marina Kalinin 2013-05-01 01:35:00 UTC
2. Who is the customer behind the request?
GSS

3. What is the nature and description of the request?
RHEV-M should have a utility to unlock failed snapshot creation to fix customers setups in case of snapshot operation failure

4. Why does the customer need this?
In order to continue using a vm, it should be released from lock.
Today, a list of manual db operations are required.
Having a script would automate this process.

5. How would the customer like to achieve this? (List the functional requirements here)
Potential failure scenarios that would require usage of this tool
- create snapshot failed
- merge snapshot failed
- snapshot preview failed 
etc -> when one of the snapshots is in a locked state.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented:
- Be able to unlock the snapshot and return VM to a usable state.
- How to know to which snapshot restore? probably by providing the involved snapshots uuids as parameters and updating their snapshot_type and status to a valid state.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
I didn't find.
I was thinking that unlock_entity.sh should handle this, but it does not look like it does. It only cleans the VM and disks status, but not snapshots.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap? is 3.2 possible?

9. Is the sales team involved in this request and do they have any additional input?
no.

10. List any affected packages or components.
dbscripts/scripts

11. Would the customer be able to assist in testing this functionality if implemented?
yes

Comment 8 Eli Mesika 2013-06-02 15:24:07 UTC
seems like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=967855
that was already merged 

Marina , please check and close as duplicate if needed


Note You need to log in before you can comment on or make changes to this bug.