Hide Forgot
Attempting to delete a volume which is still being created returns VIR_ERR_INTERNAL_ERROR. It should return VIR_ERR_OPERATION_INVALID.
Patch posted: https://www.redhat.com/archives/libvir-list/2011-May/msg01618.html
pushed upstream as 10208cc50392572c65a737a43f590c9d8467d40f on Jun 23, Daniel
1, creating a hug volume in a pool with dir type <volume> <name>vol1</name> <key>/tmp/dirpool/vol</key> <capacity unit="G">30</capacity> <allocation unit="G">30</allocation> <target> <path>/tmp/dirpool/vol</path> <format type='raw'/> </target> </volume> 2 run the following commands: # virsh vol-create dirpool ./voldirpool.xml & virsh vol-delete vol1 dirpool [1] 26923 error: Failed to delete vol vol1 error: internal error volume 'vol1' is still being allocated. it still reported internal error.
I tested it in libvirt-0.9.3-1.el6
Indeed, code inspection shows the patch to have fixed storageVolumeDownload not delete. I've submitted an additional patch upstream.
commit 618b55220ac0cfdbfb4fa4af6adf7631a9962397 Author: Dave Allan <dallan> Date: Fri Jul 15 09:47:12 2011 -0400 Fix error code for storage operations Many volume operations will fail if the volume in question is being allocated. These operations were returning VIR_ERR_INTERNAL_ERROR when they should be returning VIR_ERR_OPERATION_INVALID.
The bug has been verified on libvirt-0.9.4-rc1-1.el6 # virsh vol-create dirpool ./dirvol.xml & virsh vol-delete vol1 dirpool [1] 19930 error: Failed to delete vol vol1 error: Requested operation is not valid: volume 'vol1' is still being allocated.
retest it on rc2 version, it is fixed. libvirt-client-0.9.4-0rc2.el6.x86_64 libvirt-0.9.4-0rc2.el6.x86_64 # virsh vol-create dirpool ./dirvol.xml & virsh vol-delete vol1 dirpool [1] 20311 error: Failed to delete vol vol1 error: Requested operation is not valid: volume 'vol1' is still being allocated.
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-2011-1513.html