Bug 589427 - Example cluster name incorrect in part of "Configuration Example - NFS Over GFS" document
Summary: Example cluster name incorrect in part of "Configuration Example - NFS Over G...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: doc
Version: 4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-06 06:22 UTC by Andrew Shugg (EPITS)
Modified: 2010-10-14 18:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-14 17:59:47 UTC

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

Description Andrew Shugg (EPITS) 2010-05-06 06:22:39 UTC 
Description of problem:
"Red Hat Enterprise Linux 5: Configuration Example - NFS Over GFS"

Documentation incorrect

Section 4, "Configuring the Cluster Resources", uses the wrong name for the example cluster from section 4.3 onwards. It says "... cluster mynfs" instead of "cluster nfsclust". "mynfs" is the name given to the example global NFS Export Resource so will cause confusion.

Error is in sections 4.3 and 4.4, 7 instances in all that I counted.

Earlier sections refer to "cluster nfsclust" which is correct.

Version-Release number of selected component (if applicable):
Cluster_Config_Example_NFS_GFS(EN)-5 (2009-01-05T15:20)

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Steven J. Levine 2010-07-16 17:25:13 UTC 
I have fixed these incorrect references in the current draft of this document. These fixes will be in the next version of this document posted to redhat.com. I am scheduled to update this document by the end of July, as soon as the new procedure for posting documents publicly is set.
Comment 3 Steven J. Levine 2010-10-14 17:59:47 UTC 
The latest document is posted to redhat.com so I'm marking this as CLOSED.
Note You need to log in before you can comment on or make changes to this bug.