Bug 1111500

Summary: cman.5 incorrectly states that cluster.conf can contain up to 9 altnames for a node.
Product: Red Hat Enterprise Linux 6 Reporter: Christine Caulfield <ccaulfie>
Component: clusterAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: ccaulfie, cluster-maint, jkortus, jpayne, rpeterso, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 07:04:42 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 Christine Caulfield 2014-06-20 07:53:39 UTC
Description of problem:

The man page for cman contains this sentence: 
"Up to 9 altnames (10 interfaces in total) can be used."

Which is blatantly wrong. if you try to add more than 1 altname (2 interfaces) cman will fail to start with the message "Configuration of more than 2 rings is not supported"


Version-Release number of selected component (if applicable):
6.5, but it's probably been there since RHEL5 or even earlier!

How reproducible:
every time, 

Steps to Reproduce:
1. man cman

Actual results:
Wrong info

Expected results:
Correct info - only 1 altname is supported

Additional info:

Comment 1 Christine Caulfield 2014-06-20 08:00:23 UTC
Patch in STABLE32 branch

commit 2f05327bd8e7a072418dca45988ab5a814109258
Author: Christine Caulfield <ccaulfie>
Date:   Fri Jun 20 08:58:45 2014 +0100

    cman: fix cman.5 man page to indicate only 1 altname is allowed

Comment 4 Justin Payne 2015-03-19 15:50:56 UTC
Verified in cman-3.0.12.1-73.el6:

[root@dash-01 ~]# rpm -q cman
cman-3.0.12.1-73.el6.x86_64

[root@dash-01 ~]# man cman


Only one altname (2 interfaces in total) is valid for each node.

Comment 5 errata-xmlrpc 2015-07-22 07:04:42 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.

https://rhn.redhat.com/errata/RHBA-2015-1363.html