Bug 144909 - gulm_tool getstats reports clients as quorate when servers are not
Summary: gulm_tool getstats reports clients as quorate when servers are not
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gulm
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-12 17:18 UTC by Adam "mantis" Manthei
Modified: 2010-01-04 19:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 19:05:01 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam "mantis" Manthei 2005-01-12 17:18:30 UTC
Description of problem:
gulm_tool getstats reports clients as quorate when servers are not


Version-Release number of selected component (if applicable):
Current CVS as of now (Wed Jan 12 10:46:57 CST 2005)

How reproducible:
Always

Steps to Reproduce:
1. start ccsd on 3 nodes (2 of 3 servers in the servers list and 
   a client)
2. start lock_gulmd on the above three nodes (one server should 
   be master)
3. gulm_tool shutdown $masternode
4. gulm_tool getstats $clientnode

Actual results:

[root@trin-09 ~]# gulm_tool getstats trin-03
I_am = Arbitrating
quorum_has = 1
quorum_needs = 2
rank = 2
quorate = false
GenerationID = 1105547907194997
run time = 142
pid = 18541
verbosity = Default
failover = enabled

#
# Note that quorate=true even though the server is arbitrating
# 
[root@trin-09 ~]# gulm_tool getstats localhost
I_am = Client
quorum_has = 1
quorum_needs = 2
rank = -1
quorate = true
GenerationID = 1105547907194997
run time = 184
pid = 12695
verbosity = Default
failover = enabled

#
# ccsd should refuse this connection I believe
#
[root@trin-09 ~]# ccs_test connect
Connect successful.
 Connection descriptor = 2

Expected results:
1. gulm_tool should report that quorate==false
2. ccs_test connect should probably fail 
   (if reads are suppose to fail when there is no quorum)

Additional info:


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