Bug 890966

Summary:	nova help of add-fixed-ip command is not correct
Product:	Red Hat OpenStack	Reporter:	Ofer Blaut <oblaut>
Component:	python-novaclient	Assignee:	Jakub Ruzicka <jruzicka>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0 (Folsom)	CC:	apevec, dallan, mmagr, ndipanov
Target Milestone:	snapshot5	Keywords:	Triaged, Upstream
Target Release:	2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-novaclient-2.10.0-5.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-04 17:58:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ofer Blaut 2012-12-31 14:08:42 UTC

Description of problem:

 nova help of add-fixed-ip  command is not correct 

The current help is " Add new IP address to network."
while is should be  " Add new IP address to Instance."

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


How reproducible:


Steps to Reproduce:
1.nova help add-fixed-ip 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Nikola Dipanov 2013-01-04 16:12:11 UTC

I've posted a patch to the upstream python-novaclient: https://review.openstack.org/18963, I will move the bug to post as soon as (if) the patch gets accepted upstream.

Comment 3 Nikola Dipanov 2013-01-28 12:11:05 UTC

Upstream change has been merged so we may proceed with the backport.

Comment 6 Ofer Blaut 2013-03-18 13:52:41 UTC

Tested 
python-novaclient-2.10.0-7.el6ost.noarch


[root@puma04 ~(keystone_admin)]$ nova help  add-fixed-ip
usage: nova add-fixed-ip <server> <network-id>

Add new IP address on a network to server.

Positional arguments:
  <server>      Name or ID of server.
  <network-id>  Network ID.

Comment 8 errata-xmlrpc 2013-04-04 17:58:55 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-2013-0706.html