Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 743757

Summary: Documentation bug regarding bonding on "9.1. Cluster Does Not Form" section of Cluster Administration guide - RHEL6
Product: Red Hat Enterprise Linux 6 Reporter: Praveen <pbhaskar>
Component: doc-Cluster_AdministrationAssignee: Steven J. Levine <slevine>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: rchidamb, slevine
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-15 17:23:33 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 Praveen 2011-10-05 21:57:23 UTC
Description of problem:

RHEL 6 Cluster Administration guide says "Ensure that the interfaces you are passing cluster traffic over are not using any bonding mode other than 0 and are not using VLAN tagging." in "9.1. Cluster Does Not Form section.

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Cluster_Administration/index.html

Perhaps, mode1 is the supported bonding mode for cluster and this could be a documentation bug. RHEL-5 Administration guide suggests to use mode1 and it seems to be correct.

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

Red Hat Enterprise Linux 6 - Cluster Administration Guide

How reproducible:

Have a look at the 9.1. Cluster Does Not Form section of following doc:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Cluster_Administration/index.html

<Snippets>
Ensure that the interfaces you are passing cluster traffic over are not using any bonding mode other than 0 and are not using VLAN tagging. 
</Snippets>

Steps to Reproduce:
1. Take http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/Cluster_Administration/index.html
2. Go to "9.1. Cluster Does Not Form" section.
3. Check the statement "Ensure that the interfaces you are passing cluster traffic over are not using any bonding mode other than 0 and are not using VLAN tagging."
  
Actual results: It says "Ensure that the interfaces you are passing cluster traffic over are not using any bonding mode other than 0 and are not using VLAN tagging."


Expected results: It should be as follows since mode 1 is the supported bonding mode.

"Ensure that the interfaces you are passing cluster traffic over are not using any bonding mode other than 1 and are not using VLAN tagging."

Additional info:

Comment 2 Steven J. Levine 2011-10-07 16:42:26 UTC
I verified this with Lon Hohberger and made the change in the current working draft. I checked the draft into the svn repository so I'm moving this to MODIFIED. When I build the document I'll move this into ON_QA.