Bug 236027 - fence_xvm is incorrectly listed as "xmv" in virtual cluster
Summary: fence_xvm is incorrectly listed as "xmv" in virtual cluster
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Ryan McCabe
QA Contact: Corey Marthaler
Keywords: Desktop
Depends On: 230447
TreeView+ depends on / blocked
Reported: 2007-04-11 15:48 UTC by Ludek Smid
Modified: 2009-04-16 22:24 UTC (History)
4 users (show)

Fixed In Version: RHBA-2007-0331
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-18 20:29:46 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0331 normal SHIPPED_LIVE conga bug fix update 2007-05-18 20:26:26 UTC

Description Ludek Smid 2007-04-11 15:48:30 UTC
+++ This bug was initially created as a clone of Bug #230447 +++

Installation of the fence_xvm fencing agent incorrectly places "xvm" in the
cluster.conf file.  Result is that fencing doesn't work.  Simple change to the
right name (fence_xvm) makes fencing work

-- Additional comment from rmccabe@redhat.com on 2007-02-28 16:52 EST --
This is fixed in HEAD/RHEL4

-- Additional comment from kanderso@redhat.com on 2007-02-28 17:42 EST --
Devel ACK for RHEL5.1 - This one needs to be in an async errata release shortly
after rhel5 ga in order to allow customers to use conga to setup guest nodes in
a cluster environment.

-- Additional comment from kupcevic@redhat.com on 2007-03-30 10:24 EST --
Test with 0.9.2-4.el5 (conga and clustermon)

Comment 2 Kiersten (Kerri) Anderson 2007-04-23 16:29:56 UTC
Fixing product name.

Comment 5 Red Hat Bugzilla 2007-05-18 20:29:46 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.