Red Hat Bugzilla – Bug 756920
libvirt-python storage traceback
Last modified: 2012-06-07 15:50:19 EDT
Description of problem:
$ sudo virt-install --network network=default -r 1024 --prompt --boot menu=on --os-variant fedora16 --disk pool=home_storage,size=6,format=qcow2 --vcpus=1 -l /mnt/f16iso/ -x "divider=10 ks=http://192.168.122.1/ks.cfg" --name test8
Retrieving file .treeinfo... | 1.7 kB 00:00 ...
Retrieving file vmlinuz... | 7.9 MB 00:00 ...
Retrieving file initrd.img... | 259 MB 00:00 ...
Exception in thread Checking storage allocation:
Traceback (most recent call last):
File "/usr/lib64/python2.7/threading.py", line 552, in __bootstrap_inner
File "/usr/lib64/python2.7/threading.py", line 505, in run
File "/usr/lib/python2.7/site-packages/virtinst/Storage.py", line 1257, in _progress_thread
ignore, ignore, alloc = vol.info()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2000, in info
if ret is None: raise libvirtError ('virStorageVolGetInfo() failed', vol=self)
libvirtError: cannot open volume '/home/libvirt/images/test8.img': No such file or directory
Allocating 'test8.img' | 6.0 GB 00:00
Creating domain... | 0 B 00:00
Things appear to run, but why the traceback? The storage file wasn't there, but that is allowed, and was created in the next step. Can we get a fix for this?
Version-Release number of selected component (if applicable):
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I'm guessing that image file was deleted behind libvirt's back, but the pool wasn't refreshed so it had stale data. There are various proposals to try and make directory pools 'auto refresh' which will fix this, but otherwise this isn't strictly a bug.