Red Hat Bugzilla – Bug 1491542
failed to install due to "KeyError: 'vols'"
Last modified: 2018-04-10 07:43:30 EDT
commit ec0d3072c07165afa46c663267decb366a66457d Author: Cole Robinson <crobinso@redhat.com> Date: Wed Aug 30 10:34:17 2017 -0400 virtinst: connection: Fix error caching new pool $ virt-install --connect test:///default --name foo --ram 64 --import --disk /tmp/idontexist.img ERROR Error: --disk /tmp/idontexist.img: 'vols' Above problem makes many of our ci jobs fail, because our jobs are running in clean environments and there are no any pools in the environment. Could you help to backport this patch to downstream and rebuild a package as soon as possible? Thanks
Try to verify this bug with new build: virt-manager-1.4.2-2.el7.noarch virt-install-1.4.2-2.el7.noarch Steps: [Auto job checking] Re-trigger our CI jobs, all works well. [Manual checking] 1. Prepare a newly installed rhel7.4 system with tree: (GUI or minimal) http://download.eng.pek2.redhat.com/pub/rhel/released/RHEL-7/7.4/Server/x86_64/os/ 2. Then use yum to install virt-install related packages with latest version. such as: # yum -y install --skip-broken attr genisoimage iscsi-initiator-utils libvirt\* net-tools nmap nmap-ncat numactl libusbx patch pexpect targetcli tcpdump virt-install scsi-target-utils xfsprogs lsscsi glusterfs glusterfs-server mlocate libcgroup-tools libvirt-admin gstreamer xz fakeroot python-sphinx # rpm -q virt-install virt-install-1.4.2-1.el7.noarch 3. Use virt-install to install a domain. # virt-install --connect qemu:///system -n avocado-vt-remote-vm1 --hvm --accelerate -r 1024 --vcpus=2 --vnc --os-variant rhel7 --disk path=/var/lib/libvirt/images/rhel7.4.qcow2,bus=virtio,size=10,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:52:53:54 --import --noreboot --noautoconsole --serial pty Starting install... Allocating 'rhel7.4.qcow2' | 10 GB 00:00:00 Domain creation completed. You can restart your domain by running: virsh --connect qemu:///system start avocado-vt-remote-vm1 Result: virt-install works well. So move this bug from ON_QA to VERIFIED, thanks.
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. https://access.redhat.com/errata/RHEA-2018:0726