Bug 679932 - ccs_tool usage example for the "addnode" command is incorrect
Summary: ccs_tool usage example for the "addnode" command is incorrect
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.5
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 21:40 UTC by Alan Staples
Modified: 2012-02-10 18:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-10 18:14:42 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Alan Staples 2011-02-23 21:40:14 UTC
Description of problem:
Running "ccs_tool addnode" displays the usage for this command within ccs_tool. The example provided after the usage doesn't include a value for <nodename> as required in the usage, so instead, the parameter provided at that point in the example, "ipaddr=newnode" is used as the <nodename> incorrectly. This, if anyone uses the example to form their own addnode command lines, all of the resulting cluster nodenames will be of the format "ipaddr=nodename". Or more explicitly, within cluster.conf you'll end up with things like:
<clusternode name="ipaddr=<nodename>" ... />

instead of:
<clusternode name="<nodename>" ipaddr=w.x.y.z ... />

Version-Release number of selected component (if applicable):
cman-2.0.115-34.el5

How reproducible:
Always

Steps to Reproduce:
1. Execute "ccs_tool addnode" to display usage information
2. Attempt to follow the example to "Add a new node to the default configuration file"
3. The command succeeds, but results in unexpected cluster.conf values because the example command was wrong - not because ccs_tool did anything wrong.
  
Actual results:
The usage display provides the example...
ccs_tool addnode -n 1 -f manual ipaddr=newnode

Expected results:
Should display the example...
ccs_tool addnode -n 1 -f manual newnode

Additional info:

Comment 1 RHEL Program Management 2012-02-10 18:14:42 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


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