Bug 1316851 - VM cloned from a Cinder snapshot remains locked
Summary: VM cloned from a Cinder snapshot remains locked
Keywords:
Status: CLOSED DUPLICATE of bug 1316853
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-3.6.6
: ---
Assignee: Maor
QA Contact: Natalie Gavrielov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-11 10:09 UTC by Darryl Bond
Modified: 2016-03-23 21:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 21:07:19 UTC
oVirt Team: Storage
Embargoed:
tnisan: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1293644 0 unspecified CLOSED commands with mixed children types (CoCo/AsyncTasks) don't converge 2021-02-22 00:41:40 UTC

Internal Links: 1293644

Description Darryl Bond 2016-03-11 10:09:44 UTC
Description of problem:
A VM cloned from a ceph cinder snapshot stays in the Image Locked status forever


Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.6.3.4-1.el7.centos

How reproducible: Very


Steps to Reproduce:
1. Create a snapshot from a Cinder VM
2. Clone the snapshot to a new VM
3. Attempt to run the VM

Actual results:
VM status remains 'Image Locked' forever. VM cannot start, 'Run' menu is greyed out.

Expected results:
VM starts successfully


Additional info:
This used to work when I last tested it on 3.6.0

Comment 1 Red Hat Bugzilla Rules Engine 2016-03-13 09:21:36 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Allon Mureinik 2016-03-23 12:23:52 UTC
Darryl, this seems like the same issue as bug 1316853 (the famous bugzilla double-submit issue).
Is there something else here, or should this just be closed as a duplicate?

Comment 3 Darryl Bond 2016-03-23 21:07:19 UTC
Yes it is, this can be closed

*** This bug has been marked as a duplicate of bug 1316853 ***


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