Bug 428219 - FQDN in cluster.conf causes issues with fencing
FQDN in cluster.conf causes issues with fencing
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: cman (Show other bugs)
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Christine Caulfield
Cluster QE
: ZStream
Depends On:
Blocks: 428306
  Show dependency treegraph
Reported: 2008-01-09 18:56 EST by Corey Marthaler
Modified: 2009-04-16 15:46 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2008-0799
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-25 15:07:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to fix (616 bytes, patch)
2008-01-11 05:34 EST, Christine Caulfield
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0799 normal SHIPPED_LIVE cman bug fix and enhancement update 2008-07-25 15:06:54 EDT

  None (edit)
Description Corey Marthaler 2008-01-09 18:56:56 EST
Description of problem:
In RHEL4, cman_tool status/node reports a non FQDN even if the node in the
cluster.conf is. This will cause fencing to fail.

<?xml version="1.0"?>
<cluster config_version="4" name="TAFT">
  <fence_daemon clean_start="0" post_fail_delay="30" post_join_delay="30"/>
    <clusternode name="taft-01.lab.msp.redhat.com">

[root@taft-01 ~]# cman_tool status
Protocol version: 5.0.1
Config version: 4
Cluster name: TAFT
Cluster ID: 1156
Cluster Member: Yes
Membership state: Cluster-Member
Nodes: 4
Expected_votes: 4
Total_votes: 4
Quorum: 3
Active subsystems: 0
Node name: taft-01
Node ID: 3
Node addresses:

[root@taft-01 ~]# vi /etc/cluster/cluster.conf
[root@taft-01 ~]# cman_tool nodes
Node  Votes Exp Sts  Name
   1    1    4   M   taft-02
   2    1    4   M   taft-03
   3    1    4   M   taft-01
   4    1    4   M   taft-04

This is not the case in RHEL5

Version-Release number of selected component (if applicable):
Comment 2 RHEL Product and Program Management 2008-01-09 19:06:22 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 7 Corey Marthaler 2008-01-10 13:14:51 EST
This has to do cman not giving fenced what's in the cluster.conf file.

    <clusternode name="taft-01.dark.lab.msp.redhat.com" nodeid="1">
                <method name="1">
                        <device name="scsi" node="taft-01.dark.lab.msp.redhat.com"/>

[root@taft-02 tmp]# hostname

[root@taft-02 tmp]# cman_tool nodes
Node  Votes Exp Sts  Name
   1    1    4   M   taft-04
   2    1    4   M   taft-03
   3    1    4   M   taft-01
   4    1    4   M   taft-02
Comment 8 Christine Caulfield 2008-01-11 05:34:29 EST
Created attachment 291370 [details]
Patch to fix

The patch is attached, and quite trivial. I'd be tempted to say that the
possible repercussions of it are almost nil, but I've been horribly wrong about
that before!

It is just a cosmetic change. It does NOT change the way that cman decides
which interface or hostname to use, merely what it thinks the node names are.

One warning though: You will need to restart the whole cluster after applying
this patch. If you apply it to a single node and ask it to rejoin the cluster
it will be rejected, because the hostname doesn't natch the previous name
associated with that node ID.
Comment 10 Christine Caulfield 2008-01-11 09:24:51 EST
on RHEL4 branch:
Checking in cman/cman_tool/join_ccs.c;
/cvs/cluster/cluster/cman/cman_tool/Attic/join_ccs.c,v  <--  join_ccs.c
new revision:; previous revision:

on RHEL46 (for z-stream) branch:
Checking in cman/cman_tool/join_ccs.c;
/cvs/cluster/cluster/cman/cman_tool/Attic/join_ccs.c,v  <--  join_ccs.c
new revision:; previous revision:
Comment 13 errata-xmlrpc 2008-07-25 15:07:02 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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