Bug 707531 - volDelete returns VIR_ERR_INTERNAL_ERROR if volume is still being allocated
Summary: volDelete returns VIR_ERR_INTERNAL_ERROR if volume is still being allocated
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 707530
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 10:41 UTC by Matthew Booth
Modified: 2011-08-15 19:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 707530
Environment:
Last Closed: 2011-08-15 19:45:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Matthew Booth 2011-05-25 10:41:46 UTC
+++ This bug was initially created as a clone of Bug #707530 +++

Attempting to delete a volume which is still being created returns VIR_ERR_INTERNAL_ERROR. It should return VIR_ERR_OPERATION_INVALID.

Comment 2 Huming Jiang 2011-06-03 05:57:41 UTC
Could reproduce this bug on the following components of rh5.6:
libvirt-0.8.2-15.el5
virt-manager-0.6.1-13.el5
kernel-2.6.18-238.el5

Steps:
open two terminal at the same time:
on one terminal:
# virsh vol-create-as default vol-test2.raw 4194304000 --allocation 3024347136
--format raw
(running)

on the other terminal:
#virsh vol-delete --pool default vol-test2.raw
error: Failed to delete vol vol-test2.raw
error: internal error volume 'vol-test2.raw' is still being allocated.

The error message is from the src/storage/storage_driver.c, in the package "libvirt-0.8.2-15.el5.src.rpm"
... 
   if (vol->building) {
        virStorageReportError(VIR_ERR_INTERNAL_ERROR,
                              _("volume '%s' is still being allocated."),
                              vol->name);
        goto cleanup;
    }
...

Comment 5 RHEL Program Management 2011-08-15 19:45:56 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


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