Hide Forgot
We aren't properly raising error messages if volume creation fails. See https://bugzilla.redhat.com/show_bug.cgi?id=673028 as an example. Fixed upstream: http://hg.fedorahosted.org/hg/python-virtinst/rev/6927884e174e
Fixed in python-virtinst-0.500.5-2.el6
Verified with python-virtinst-0.500.5-2.el6.noarch, it now can raise the error messages if specifying a wrong volume format type. Move to VERIFIED. # virt-install -n test1 -r 512 --cdrom /var/lib/libvirt/boot/Fedora-14-i686-Live-Desktop.iso --vcpus=2 --disk path=/var/lib/libvirt/images/test1.img,size=5,format=asdf --hvm --accelerate --os-variant=virtio26 --network network:default --noreboot --vnc Starting install... ERROR internal error unknown disk format 'asdf' for /var/lib/libvirt/images/test1.img Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start test1 otherwise, please restart your installation.
verified this bug with: Linux localhost.localdomain 2.6.32-130.el6.x86_64 #1 SMP Tue Apr 5 19:58:31 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux python-virtinst-0.500.5-3.el6.noarch libvirt-0.8.7-17.el6.x86_64 passed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * When specifying a wrong volume format type an error message would not display. This change informs the user by raising the appropriate error message when the storage pool cannot find the appropriate volume. (BZ#683182)
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -* When specifying a wrong volume format type an error message would not display. This change informs the user by raising the appropriate error message when the storage pool cannot find the appropriate volume. (BZ#683182)+When specifying a wrong volume format type an error message would not display. This change informs the user by raising the appropriate error message when the storage pool cannot find the appropriate volume.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0636.html