Description: Using a typical virt-install command line to create a new guest (it's new, so has no storage allocated yet), we get a backtrace. Everything proceeds fine, creating the storage as it should. See below $ virt-install -n guest -l http://$SERVER/nightly/latest-RHEL-7/compose/Server/aarch64/os/ --vcpus=4 --memory 4096 --disk size=6 --network default --boot uefi Starting install... Retrieving file vmlinuz... | 11 MB 00:00:05 !!! Retrieving file initrd.img... | 62 MB 00:00:08 !!! Exception in thread Checking storage allocation: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/share/virt-manager/virtinst/storage.py", line 838, in _progress_thread ignore, ignore, alloc = vol.info() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3374, in info if ret is None: raise libvirtError ('virStorageVolGetInfo() failed', vol=self) libvirtError: Storage volume not found: no storage vol with matching path '/home/drjones/.local/libvirt/images/guest.qcow2' Allocating 'guest.qcow2' | 6.0 GB 00:00:00 Creating domain... | 0 B 00:00:01 ... Expected results: No backtrace
Hi, I've tried to reproduce it, but I was not able to hit any exception. Could you please try it again with latest virt-install and libvirt packages and using --debug option?
(In reply to Pavel Hrdina from comment #2) > Hi, I've tried to reproduce it, but I was not able to hit any exception. > Could you please try it again with latest virt-install and libvirt packages > and using --debug option? Still reproduces with virt-install-1.2.1-8.el7.noarch, which is the version we currently have in the rhelsa virt repo. If it's fixed with a later version, then I guess we need to tag a later build to get that into the repo. Are there 7.3 builds for virt-install and libvirt that we can start taging for rhelsa-7.3 work? Thanks, drew
I'll be cutting a new virt-manager build before monday, at which point we should pull it into RHEL. So... soon :)
Upstream commit: commit 0ccbcd8883c17097b9a3bc5975c1a83517ab0b22 Author: Pavel Hrdina <phrdina> Date: Thu Nov 19 14:48:25 2015 +0100 storage: remove attempt counter from disk allocation thread Remove the lookup counter from _progress_thread, it's not necessary, the loop is terminated by _install_finished boolean. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1270277 Signed-off-by: Pavel Hrdina <phrdina>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
This bug is now fixed, the installation doesn't print the backtrace anymore. This can be moved to verified.
Refer to comment 9,move the bug to VERIFIED.