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 230469

Summary: Must manually edit cluster.conf on the dom0 cluster to add "<fence_xvmd/>"
Product: Red Hat Enterprise Linux 5 Reporter: Rob Kenna <rkenna>
Component: congaAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: Corey Marthaler <cmarthal>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: cluster-maint, kanderso, kupcevic, rmccabe, tscherf
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHSA-2007-0640 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 15:37:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 230466, 236055    

Description Rob Kenna 2007-02-28 21:52:15 UTC
For fence_xvmd support on a Dom0 cluster you must manually edit cluster.conf and
add  "<fence_xvmd/>" which signals that fence_xvmd must be run.  This runs
counter to the automation of Conga

Comment 1 Ryan McCabe 2007-02-28 21:56:42 UTC
This is fixed in HEAD/RHEL4

Comment 2 Kiersten (Kerri) Anderson 2007-02-28 22:37:23 UTC
Unable to do a clean setup of a virtual cluster without this capability.  Need
to include this in an async errata release soon after day0 for rhel5.

Comment 5 Stanko Kupcevic 2007-03-30 14:32:43 UTC
Test with 0.9.2-4.el5 (conga and clustermon)

Comment 6 Ryan McCabe 2007-04-10 16:30:53 UTC
*** Bug 225558 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2007-11-07 15:37:25 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.