Bug 707494

Summary:	It is not possible to delete a volume while it's being created
Product:	Red Hat Enterprise Linux 7	Reporter:	Matthew Booth <mbooth>
Component:	libvirt	Assignee:	Michal Privoznik <mprivozn>
Status:	CLOSED DEFERRED	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	cwei, dyuan, jdenemar, mprivozn, mzhan, rbalakri, rjones, veillard, yanyang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	707495 (view as bug list)		Environment:
Last Closed:	2016-02-17 10:33:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	707495, 707496

Description Matthew Booth 2011-05-25 09:03:19 UTC

Volume creation can take a long time. Attempting to delete a volume which is still being created returns an error. It is not currently possible to work round this, for example with an API to cancel the creation process.

This impacts V2V. V2V removes all inconsistent volumes if the conversion process fails or is interrupted. This cleanup will fail if the user hits Ctrl-C during a long-running volume creation, because the volume cannot be deleted. This will cause subsequent V2V conversions to fail because the volume already exists.

Comment 4 Dave Allan 2012-05-14 16:02:16 UTC

*** Bug 772704 has been marked as a duplicate of this bug. ***

Comment 11 Jiri Denemark 2014-04-04 21:36:34 UTC

This bug was not selected to be addressed in Red Hat Enterprise Linux 6. We will look at it again within the Red Hat Enterprise Linux 7 product.

Comment 12 Michal Privoznik 2014-05-29 13:48:43 UTC

Fixed upstream:

commit eb54426659888bf04fdef409afaccf8c0fd199a0
Author:     Michal Privoznik <mprivozn>
AuthorDate: Wed Apr 16 15:16:20 2014 +0200
Commit:     Michal Privoznik <mprivozn>
CommitDate: Tue May 6 10:24:44 2014 +0200

    storageVolCreateXMLFrom: Allow multiple accesses to origvol
    
    When creating a new volume, it is possible to copy data into it from
    another already existing volume (referred to as @origvol). Obviously,
    the read-only access to @origvol is required, which is thread safe
    (probably not performance-wise though). However, with current code
    both @newvol and @origvol are marked as building for the time of
    copying data from the @origvol to @newvol. The rationale behind
    is to disallow some operations on both @origvol and @newvol, e.g.
    vol-wipe, vol-delete, vol-download. While it makes sense to not allow
    such operations on partly copied mirror, but it doesn't make sense to
    disallow vol-create or vol-download on the source (@origvol).
    
    Signed-off-by: Michal Privoznik <mprivozn>

v1.2.4-18-geb54426  (so you have to use the v1.2.5-rc1~111 release)

Comment 13 Jiri Denemark 2014-06-23 13:56:40 UTC

Actually, the commit from comment 12 fixes another bug, see bug 1069552.

Comment 18 Richard W.M. Jones 2016-02-17 10:33:40 UTC

I'm closing this.  The fix was originally requested for virt-v2v,
but the new version of virt-v2v does not use libvirt for volume
creation, hence this is no longer a problem.