Bug 687526

Summary: virt-install puts non-error output on stderr
Product: Red Hat Enterprise Linux 6 Reporter: Greg Nichols <gnichols>
Component: python-virtinstAssignee: Cole Robinson <crobinso>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dyuan, hjiang, mzhan, rlandry, zpeng
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
No description necessary
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 16:15:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 682115, 865546    

Description Greg Nichols 2011-03-15 15:07:25 UTC
Description of problem:

The virt-install script produces non-error output on stderr.  This causes
the v7 certification suite to fail virtualization tests.

Version-Release number of selected component (if applicable):

RHEL 6.1, python-virtinst 0.500.5-1.el6


Steps to Reproduce:

[root@hp-xw8400-01 ~]# virt-install --name v7x86_64 --ram 512 --disk
path=/var/lib/libvirt/images/v7x86_64.img --disk
path=/var/lib/libvirt/images/v7data.img --network network:default --vnc
--import  --noreboot --noautoconsole 2>stderr.txt

Starting install...
Domain creation completed. You can restart your domain by running:
  virsh --connect qemu:///system start v7x86_64
[root@hp-xw8400-01 ~]# more stderr.txt
Creating domain...                                       |    0 B     00:00
[root@hp-xw8400-01 ~]#

Comment 2 RHEL Program Management 2011-04-04 02:15:12 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
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.

Comment 3 Cole Robinson 2011-04-07 16:19:11 UTC
Weird, by default the progress reporting is sent to stderr. Fixed upstream now:

http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=02f68f6650b60b65e6e26414f2f3bad4630ed6d8

virt-install can still print stderr output even if the command isn't going to fail, like various warnings (network doesn't support PXE is one of them). I'd recommend changing your tests to not report failure if there is stderr output, maybe just a warning or something.

Since this isn't a regression and isn't high priority, moving to 6.2

Comment 4 Cole Robinson 2011-07-28 15:34:04 UTC
Fixed in python-virtinst-0.600.0-1.el6

Comment 6 Huming Jiang 2011-08-02 11:06:46 UTC
Verified with the following components:
python-virtinst-0.600.0-1.el6.
libvirt-0.9.4-0rc1.el6.x86_64
kernel-2.6.32-171.el6.x86_64
qemu-kvm-0.12.1.2-2.174.el6.x86_64


Steps:

1. # virt-install --name test -r 512 --disk path=/var/lib/libvirt/images/demo.img --disk path=/var/lib/libvirt/images/test1.img --network network:default --vnc --import --noreboot --noautoconsole 2>stderr.txt

Starting install...
Creating domain...                                       |    0 B     00:00     
Domain creation completed. You can restart your domain by running:
  virsh --connect qemu:///system start test
[root@jhm images]# more stderr.txt 
[root@jhm images]# 


2. # virt-install --name test -r 512 --disk path=/var/lib/libvirt/images/demo.img --disk path=/var/lib/libvirt/images/tes.img --network network:default --vnc --import --noreboot --noautoconsole 2>stderr.txt
[root@jhm images]# more stderr.txt 
ERROR    Error with storage parameters: Size must be specified for non existent 
volume path '/var/lib/libvirt/images/tes.img'

Comment 7 Cole Robinson 2011-11-07 16:50:47 UTC
    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:
No description necessary

Comment 8 errata-xmlrpc 2011-12-06 16:15:59 UTC
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-2011-1643.html