Bug 1002490 - virsh cpu-baseline doesn't print error message for empty file argument
Summary: virsh cpu-baseline doesn't print error message for empty file argument
Keywords:
Status: CLOSED DUPLICATE of bug 889276
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 10:19 UTC by Pavel Hrdina
Modified: 2013-09-04 13:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-04 13:41:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pavel Hrdina 2013-08-29 10:19:01 UTC 
Description of problem:
The virsh command 'cpu-baseline' doesn't print eny error message into stderr for emtpy file argument. This bug has been discovered by libvirt-autotest.

Version-Release number of selected component (if applicable):
libvirt-0.10.2-23.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. virsh cpu-baseline ''

Actual results:
echo $? -> 1
stderr -> nothing

Expected results:
echo $? -> 1
stderr -> error: Failed to get option 'file': Option argument is empty

Additional info:
The error message is from upstream libvirt.
Comment 1 Peter Krempa 2013-08-29 10:26:34 UTC 
This was fixed upstream by commit:

commit fa956d9055c6fc1aaf672172343172da113f5e47
Author: Peter Krempa <pkrempa>
Date:   Mon Jan 21 15:39:18 2013 +0100

    virsh-domain: Update domain commands to use vshCommandOptStringReq
Comment 4 Jiri Denemark 2013-09-04 13:41:44 UTC 

*** This bug has been marked as a duplicate of bug 889276 ***
Note You need to log in before you can comment on or make changes to this bug.