Bug 733011

Summary: Device name mispelled on --addfencedev
Product: Red Hat Enterprise Linux 6 Reporter: amedeo
Component: doc-Cluster_AdministrationAssignee: Steven J. Levine <slevine>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1CC: cfeist, jskeoch, slevine
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 22:10:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description amedeo 2011-08-24 13:04:22 UTC
On document Cluster_Administration(EN)-6 (2011-05-19T16:26) (latest available on-line) at chapter 5.5 (1) when there are an example on creating fence device "myfence" by this command:

# ccs -h node1 --addfencedev myfence agent=fence_apc ipaddr=apc_ip_example login=login_example passwd=password_example

the resulting xml from cluster.conf configuration file has device name setting to "apc" and not to "myfence":

<fencedevices>
      <fencedevice agent="fence_apc" ipaddr="apc_ip_example" login="login_example" name="apc" passwd="password_example"/>
</fencedevices>


1) http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/s1-config-fence-devices-ccs-CA.html

Best Regards
Amedeo Salvati

Comment 2 Steven J. Levine 2011-08-24 15:17:54 UTC
There is a mistake in the document, but this description is backwards. The ccs example command in the document is this:

ccs -h node1 --addfencedev myfence agent=fence_apc ipaddr=apc_ip_example login=login_example passwd=password_example

But the resulting cluster.conf file the document provides is this:

<fencedevices>
      <fencedevice agent="fence_apc" ipaddr="apc_ip_example" login="login_example" name="apc" passwd="password_example"/>
</fencedevices>

So either the command should specify apc as the name, or the cluster.conf file should specify myfence. Since the rest of the section calls the device "myfence" I'll fix the cluster.conf file example to note this:

<fencedevices>
      <fencedevice agent="fence_apc" ipaddr="apc_ip_example"
login="login_example" name="myfence" passwd="password_example"/>
</fencedevices>

That should make this consistent. I have fixed this in my working draft.

Comment 5 Steven J. Levine 2011-11-14 22:10:17 UTC
Latest build for 6.2 GA release:
Red_Hat_Enterprise_Linux-Cluster_Administration-6-web-en-US-0-114_el6eng

Moving to CLOSED.