Bug 469103 - Quorum not formed before gfs starts with one node in a "4-node + qdisk" configuration
Summary: Quorum not formed before gfs starts with one node in a "4-node + qdisk" confi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: cman
Version: 4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 436381
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-29 21:35 UTC by Jeffrey Needham
Modified: 2009-05-18 21:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-18 21:18:41 UTC
Embargoed:

Attachments (Terms of Use)
Here's a fix anyhow. :) (1.67 KB, patch)
2009-02-27 22:19 UTC, Lon Hohberger 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1053 0 normal SHIPPED_LIVE cman bug-fix update 2009-05-18 21:18:38 UTC

Comment 1 Lon Hohberger 2009-02-27 22:16:51 UTC 
I'm not sure this applies to RHEL4 - we start CMAN, then start qdiskd, then fenced.  So, this ought to not happen on RHEL4.  Booting would just be delayed for a really long time in some cases (7 or so minutes by the looks of it).
Comment 2 Lon Hohberger 2009-02-27 22:19:13 UTC 
Created attachment 333547 [details]
Here's a fix anyhow. :)
Comment 3 Lon Hohberger 2009-02-27 22:22:53 UTC 
http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=6667a111f43a4344996d861e1b0f8e169f163a8c

Pushed to RHEL4 branch.
Comment 6 errata-xmlrpc 2009-05-18 21:18:41 UTC 
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 therefore 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.

http://rhn.redhat.com/errata/RHBA-2009-1053.html
Note You need to log in before you can comment on or make changes to this bug.