Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
qcow should not be in error info when use virt-image create a guest with invalid disk format in XML
Version-Release number of selected component (if applicable):
virt-manager-0.9.0-21.el6.x86_64
python-virtinst-0.600.0-21.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1.Prepare a virtual image XML descriptor file with an invalid disk format, such as "aaaa".
# cat image.xml
<image>
<name>demo</name>
<domain>
<boot type="hvm">
<guest>
<arch>x86_64</arch>
</guest>
<os>
<loader dev="hd"/>
</os>
<drive disk="mydisk" target="hda"/>
</boot>
<devices>
<vcpu>1</vcpu>
<memory>262144</memory>
<graphics/>
</devices>
</domain>
<storage>
<disk id="mydisk" file="/var/lib/libvirt/images/rr66.img" use="system" format="aaaa"/>
</storage>
</image>
2.Create a virtual machine from image.xml
# virt-image image.xml
ERROR Cannot parse 'image.xml': The format for disk /var/lib/libvirt/images/rr66.img must be one of raw,qcow,qcow2,vmdk,iso
3.Check the format description in manual.
#man 5 virt-image
...
· the format attribute giving the format of the disk file. Currently, this can be one of: "raw", "iso",
"qcow2", or "vmdk".
...
Actual results:
The format for disk /var/lib/libvirt/images/rr66.img must be one of raw,qcow,qcow2,vmdk,iso.
Expected results:
Error message should not include "qcow" format inside.
Additional info:
I can reproduce with package:
python-virtinst-0.600.0-21.el6.noarch
verified with new build:
python-virtinst-0.600.0-22.el6.noarch
steps:
1.Prepare a virtual image XML descriptor file with an invalid disk format, such as "aaaa".
# cat images.xml
<image>
<name>demo</name>
<domain>
<boot type="hvm">
<guest>
<arch>x86_64</arch>
</guest>
<os>
<loader dev="hd"/>
</os>
<drive disk="mydisk" target="hda"/>
</boot>
<devices>
<vcpu>1</vcpu>
<memory>262144</memory>
<graphics/>
</devices>
</domain>
<storage>
<disk id="mydisk" file="/var/lib/libvirt/images/test1.img" use="system" format="aaaa"/>
</storage>
</image>
2.Create a virtual machine from image.xml
# virt-image images.xml
ERROR Cannot parse 'images.xml': The format for disk /var/lib/libvirt/images/test1.img must be one of raw,qcow2,vmdk,iso
Since the format showing is coincident with manual page.
# man 5 virt-image
· the format attribute giving the format of the disk file. Currently,
this can be one of: "raw", "iso", "qcow2", or "vmdk".
there is no "qcow" format showing, move to verified.
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-2014-1444.html
Description of problem: qcow should not be in error info when use virt-image create a guest with invalid disk format in XML Version-Release number of selected component (if applicable): virt-manager-0.9.0-21.el6.x86_64 python-virtinst-0.600.0-21.el6.noarch How reproducible: 100% Steps to Reproduce: 1.Prepare a virtual image XML descriptor file with an invalid disk format, such as "aaaa". # cat image.xml <image> <name>demo</name> <domain> <boot type="hvm"> <guest> <arch>x86_64</arch> </guest> <os> <loader dev="hd"/> </os> <drive disk="mydisk" target="hda"/> </boot> <devices> <vcpu>1</vcpu> <memory>262144</memory> <graphics/> </devices> </domain> <storage> <disk id="mydisk" file="/var/lib/libvirt/images/rr66.img" use="system" format="aaaa"/> </storage> </image> 2.Create a virtual machine from image.xml # virt-image image.xml ERROR Cannot parse 'image.xml': The format for disk /var/lib/libvirt/images/rr66.img must be one of raw,qcow,qcow2,vmdk,iso 3.Check the format description in manual. #man 5 virt-image ... · the format attribute giving the format of the disk file. Currently, this can be one of: "raw", "iso", "qcow2", or "vmdk". ... Actual results: The format for disk /var/lib/libvirt/images/rr66.img must be one of raw,qcow,qcow2,vmdk,iso. Expected results: Error message should not include "qcow" format inside. Additional info: