Bug 849079 - A typo of virt-install error message when both parameters '--nonetworks' and '--bridge' included
Summary: A typo of virt-install error message when both parameters '--nonetworks' and ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-17 09:06 UTC by Cui Lei
Modified: 2014-07-06 19:31 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-13 01:32:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Cui Lei 2012-08-17 09:06:18 UTC
Description of problem:
Run a virt-install command with both parameters '--nonetworks' and '--bridge', such as:
# virt-install -n demo -r 1024 --disk path=/var/lib/libvirt/images/demo.img,size=6 --nonetworks --bridge=breth0sd -c /dev/cdrom
ERROR    Cannot use --bridges with --nonetworks

There is a typo of above error message, the '--bridges' should be changed to '--bridge'.
As '--bridges' was not valid parameters in virt-install. If you use '--bridges' in virt-install command, error message should pop up as:
"virt-install: error: no such option: --bridges"


Version-Release number of selected component (if applicable):
python-virtinst-0.600.0-8.el6.noarch

How reproducible:
100%

Steps to Reproduce:
Run a virt-install command with both parameters '--nonetworks' and '--bridge', such as:
# virt-install -n demo -r 1024 --disk path=/var/lib/libvirt/images/demo.img,size=6 --nonetworks --bridge=breth0sd -c /dev/cdrom
check the error message

Actual results:
ERROR    Cannot use --bridges with --nonetworks

Expect result:
ERROR    Cannot use --bridge with --nonetworks

Comment 2 Alex Jia 2012-08-17 10:55:27 UTC
Patch for upstream:
https://www.redhat.com/archives/virt-tools-list/2012-August/msg00044.html

Comment 3 Cole Robinson 2013-06-13 01:32:16 UTC
Fixed upstream a while ago.


Note You need to log in before you can comment on or make changes to this bug.