Bug 1000617

Summary: shutting down the cluster fails
Product: Red Hat Enterprise Linux 6 Reporter: Corey Marthaler <cmarthal>
Component: clusterAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5CC: ccaulfie, cluster-maint, fdinitto, rpeterso, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-27 06:07:36 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 Corey Marthaler 2013-08-23 20:58:49 UTC 
What am I doing wrong/what did I forget?

Description of problem:
[root@taft-01 ~]# getenforce
Permissive
[root@taft-01 ~]# service cman start
Starting cluster: 
   Checking if cluster has been disabled at boot...        [  OK  ]
   Checking Network Manager...                             [  OK  ]
   Global setup...                                         [  OK  ]
   Loading kernel modules...                               [  OK  ]
   Mounting configfs...                                    [  OK  ]
   Starting cman...                                        [  OK  ]
   Waiting for quorum...                                   [  OK  ]
   Starting fenced...                                      [  OK  ]
   Starting dlm_controld...                                [  OK  ]
   Tuning DLM kernel config...                             [  OK  ]
   Starting gfs_controld...                                [  OK  ]
   Unfencing self...                                       [  OK  ]
   Joining fence domain...                                 [  OK  ]
[root@taft-01 ~]# service cman stop
Stopping cluster: 
   Leaving fence domain...                                 [  OK  ]
   Stopping gfs_controld...                                [  OK  ]
   Stopping dlm_controld...                                [  OK  ]
   Stopping fenced...                                      [  OK  ]
   Stopping cman... Timed-out waiting for cluster

Aug 23 15:49:49 taft-01 crmd[2139]:   notice: cman_event_callback: CMAN wants to shut down: optional

Version-Release number of selected component (if applicable):
corosync-1.4.1-17.el6.x86_64
cman-3.0.12.1-56.el6.x86_64
pacemaker-1.1.10-6.el6.x86_64

How reproducible:
Everytime
Comment 2 Fabio Massimo Di Nitto 2013-08-27 06:07:36 UTC 
You need to shutdown cman users first (in this case pacemaker).

Pacemaker can refuse cman to shutdown if it's in the process to do something.

this is no different on what you do with rgmanager combination.

cman start
rgmanager start
..
rgmanager stop
cman stop