Bug 683320
Summary: | virt-install: unmatched error info with --print-xml option | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nan Zhang <nzhang> |
Component: | python-virtinst | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | dallan, dyuan, llim, mhideo, mjenner, syeghiay, xen-maint, zpeng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
virt install would display the wrong error message when invoking --print-xml. This fix ensures the correct error message is displayed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-05-19 13:45:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nan Zhang
2011-03-09 06:02:14 UTC
Fixed in python-virtinst-0.500.5-2.el6 Verified on python-virtinst-0.500.5-2.el6.noarch, not fixed. # rpm -qa|grep python-virtinst python-virtinst-0.500.5-2.el6.noarch #virt-install -n foo -r 512 -f /tmp/foo.img -s 6 --cdrom /tmp/boot.iso --print-xml --vnc ERROR --xml-only can only be used with guests that do not have an installation phase (--import, --boot, etc.). To see all generated XML, please use --print-step all. the bug not fixed completely,expected error messages is: ERROR --print-xml can only be used with guests that do not have an installation phase (--import, --boot, etc.). To see all generated XML, please use --print-step all. Argh, I keep messing this fix up! :) Upstream now http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=090517f55533428acbabd95760743132f10cad3f Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as an exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Should be fixed in python-virtinst-0.500.5-3.el6 Verified on python-virtinst-0.500.5-3.el6.noarch,fixed. # rpm -qa|grep python-virtinst python-virtinst-0.500.5-3.el6.noarch ]# virt-install -n foo -r 512 -f /tmp/test.img -s 6 --cdrom /tmp/boot.iso --print-xml --vnc ERROR --print-xml can only be used with guests that do not have an installation phase (--import, --boot, etc.). To see all generated XML, please use --print-step all. the bug fixed,change ot Verified. 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: * virt install would display the wrong error message when invoking --print-xml. This fix ensures the correct error message is displayed. (BZ#683320) 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 @@ -* virt install would display the wrong error message when invoking --print-xml. This fix ensures the correct error message is displayed. (BZ#683320)+virt install would display the wrong error message when invoking --print-xml. This fix ensures the correct error message is displayed. 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 |