Bug 698992

Summary: cluster/cman not starting up. "[TOTEM ] The consensus timeout expired."
Product: Red Hat Enterprise Linux 6 Reporter: Christian Horn <chorn>
Component: clusterAssignee: Fabio Massimo Di Nitto <fdinitto>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: ccaulfie, cluster-maint, lhh, rpeterso, sdake, teigland
Target Milestone: rc   
Target Release: 6.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-25 07:35:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
cluster.conf two used for testing
none
cluster.conf with configured qdisk, produces same result
none
corosync.log of one of the 2 nodes none

Description Christian Horn 2011-04-22 15:00:21 UTC
Created attachment 494247 [details]
cluster.conf two used for testing

Description of problem: 
  Starting cman... [FAILED], cluster not starting

Version-Release number of selected component (if applicable):
  rhel6.1 beta snapshot 4

How reproducible:
  always

Steps to Reproduce:
1. setup 2 nodes, virtualized fine
2. yum -y install cman rgmanager
3. deploy cluster.conf_twonode as /etc/cluster/cluster.conf on both nodes
4. service cman start
  
Actual results:
  Starting cman... [FAILED]

Expected results:
  Starting cman... [OK]

Additional info:
  Using a config with qdisk brings up the same problem, qdisk via
  iscsi initiator was used here, cluster.conf_qdisk is attached.

Comment 2 Christian Horn 2011-04-22 15:02:13 UTC
Created attachment 494248 [details]
cluster.conf with configured qdisk, produces same result

Comment 3 Christian Horn 2011-04-22 15:03:46 UTC
Created attachment 494249 [details]
corosync.log of one of the 2 nodes

Comment 5 RHEL Program Management 2011-04-23 06:00:34 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Steven Dake 2011-04-25 02:16:36 UTC
Christian,

It looks to me like your firewall is enabled.

Is it configured properly?

Regards
-steve

Comment 7 Christian Horn 2011-04-25 07:28:47 UTC
Steven,

sorry for the noise - true, the firwall was established.
Did multiple installations to verify the behaviour, all with the new
virt-install setup here that deployed a firewall..
The cluster comes up now in both configurations, two_node as well as qdisk.

Sorry again, Christian