Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230972 - Qdisk daemon unable to be started on all members in Xen cluster setup
Summary: Qdisk daemon unable to be started on all members in Xen cluster setup
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
: 230971 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-05 08:04 UTC by Dean Samuels
Modified: 2018-10-19 19:51 UTC (History)
2 users (show)

Fixed In Version: RHBA-2007-0575
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-11-07 16:59:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
update patch for RHEL5.0 qdisk -> RHEL5 stable development (deleted)
2007-03-06 15:52 UTC, Lon Hohberger
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0575 normal SHIPPED_LIVE cman bug fix update 2007-10-31 12:26:24 UTC

Description Dean Samuels 2007-03-05 08:04:09 UTC
Description of problem:
Starting qdisk service fails on all Xen domU cluster members (2-node cluster). 
cluster.conf configuration as follows:
<quorumd device="/dev/sdb" interval="1" label="quorum" min_score="3" tko
="10" votes="3">
                <heuristic interval="2" program="ping b -c1 -t1" score="1"/>

Version-Release number of selected component (if applicable):

How reproducible:
Configure qurourm device via system-config-cluster.  Create quorum disk seen by
all members via mkqdisk command.  Attempt to start qdiskd daemon fails.

Steps to Reproduce:
1.  Create cluster with quorum device via system-config-cluster
2.  Add in apprppriate heuristics
3.  Start cman services - successful
4.  Start qdiskd service -fails with errror 
"Could not determine local node ID; cannot start"
Actual results:
Qdiskd fails to start so quorum device cannot be used as part of cluster.

Expected results:
Qdiskd starts successfully and quorum device part of cluster, seen via clustat
command.  Optional status file also updated as specified in cluster.conf.

Additional info:

Comment 1 Christine Caulfield 2007-03-05 09:18:47 UTC
*** Bug 230971 has been marked as a duplicate of this bug. ***

Comment 2 Lon Hohberger 2007-03-05 15:56:40 UTC
This is fixed in 4.5/5.1, or should be.   It may warrant an errata against 5.0.

Comment 3 Dean Samuels 2007-03-05 21:03:03 UTC
Can the updated packages be made available so I may test?  I'm assuming it's an
update to the cman package?

Comment 4 Lon Hohberger 2007-03-06 14:53:22 UTC
I have some cman & cman-kernel packages with just qdisk-required updates for
42.0.3 & 42.0.8 RHEL4 errata kernels here:

Comment 5 Lon Hohberger 2007-03-06 15:02:03 UTC
Oh - I missed that this is RHEL5.  I'll build something shortly.

Comment 6 Lon Hohberger 2007-03-06 15:52:12 UTC
Created attachment 149344 [details]
update patch for RHEL5.0 qdisk -> RHEL5 stable development

Comment 7 Robert Hell 2007-03-30 09:17:33 UTC
Hi! I got the same Problem with RHEL5. Will there be an errata or how can i get 
a supported fix?

Comment 8 Edouard Bourguignon 2007-04-20 08:57:30 UTC
same problem on FC6

Comment 9 Kiersten (Kerri) Anderson 2007-04-23 16:49:44 UTC
Fixing Product Name.  Cluster Suite was merged into Red Hat Enterpise Linux for
5.0.  In addition dlm, fence and ccs were merged into the cman package, so
bugzilla should reflect package name where those utilities are located.

Comment 11 RHEL Product and Program Management 2007-05-07 19:06:03 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 12 Robert Hell 2007-05-29 13:08:06 UTC
Any news if there will be an official errata for this problem?

Comment 16 Lon Hohberger 2007-08-27 16:24:24 UTC
This is fixed in 5.1 beta - give it a spin?

Comment 20 errata-xmlrpc 2007-11-07 16:59:10 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 the 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.

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