RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 596046 - Qdisk: quorum is recalculated after node abruptly leaves cluster
Summary: Qdisk: quorum is recalculated after node abruptly leaves cluster
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 595394
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 08:26 UTC by Christine Caulfield
Modified: 2010-11-10 19:59 UTC (History)
11 users (show)

Fixed In Version: cluster-3.0.12-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 595394
Environment:
Last Closed: 2010-11-10 19:59:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch for stable3 (1.12 KB, patch)
2010-05-26 08:34 UTC, Christine Caulfield
no flags Details | Diff

Comment 1 Christine Caulfield 2010-05-26 08:34:02 UTC
Created attachment 416713 [details]
Patch for stable3

This is the patch for STABLE3. I'll commit it if it passes a little more testing.

Comment 3 Christine Caulfield 2010-05-26 14:36:05 UTC
commit f288015025489cb35230c61f82d02c3d70e4a40e
Author: Christine Caulfield <ccaulfie>
Date:   Wed May 26 09:51:34 2010 +0100

    cman: fix quorum recalculation when a node is externally killed

Comment 5 Dean Jansa 2010-08-24 20:21:06 UTC
[root@marathon-01 ~]# cman_tool status
Version: 6.2.0
Config Version: 4
Cluster Name: marathon
Cluster Id: 20778
Cluster Member: Yes
Cluster Generation: 2756
Membership state: Cluster-Member
Nodes: 5
Expected votes: 5
Quorum device votes: 4
Total votes: 8
Node votes: 1
Quorum: 5  
Active subsystems: 9
Flags: 
Ports Bound: 0  
Node name: marathon-01
Node ID: 1
Multicast addresses: 239.192.81.123 
Node addresses: 10.15.89.71 


==== Crash marathon-05 ====


[root@marathon-01 ~]# cman_tool status
Version: 6.2.0
Config Version: 4
Cluster Name: marathon
Cluster Id: 20778
Cluster Member: Yes
Cluster Generation: 2760
Membership state: Cluster-Member
Nodes: 4
Expected votes: 5
Quorum device votes: 4
Total votes: 8
Node votes: 1
Quorum: 5  
Active subsystems: 9
Flags: 
Ports Bound: 0  
Node name: marathon-01
Node ID: 1
Multicast addresses: 239.192.81.123 
Node addresses: 10.15.89.71

Comment 6 releng-rhel@redhat.com 2010-11-10 19:59:20 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. 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.