Bug 161974 - creates borken fence_manual configuration
creates borken fence_manual configuration
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-06-28 16:20 EDT by Katriel Traum
Modified: 2009-04-16 16:09 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2005-753
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-07 12:48:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Katriel Traum 2005-06-28 16:20:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Creating a fence_manual agent and attaching it to a node creates a cluter.conf without "nodename" or "ipaddr" config option which causes fence_manual to fail on node fencing.

syslog reports:
Jun 28 23:04:11 node1 fenced[1839]: fence "node2" failed
Jun 28 23:04:16 node1 fenced[1839]: fencing node "node2"
Jun 28 23:04:16 node1 fenced[1839]: agent "fence_manual" reports: failed: fence_manual no node name

cluster.conf section looks like:
<method name="1">
     <device name="manfence"/>

should be:
<method name="1">
     <device name="manfence" nodename="node name">

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

How reproducible:

Steps to Reproduce:
1.Create new config with system-config-cluster
2.Create fence_manual fencing device, attach to node, save cnew config
3.New config is invalid

Additional info:
Comment 1 Stanko Kupcevic 2005-08-04 16:22:09 EDT
Fixed in Errata Candidate
Comment 2 Corey Marthaler 2005-09-07 13:10:59 EDT
fix verified in 1.0.15
Comment 3 Red Hat Bugzilla 2005-10-07 12:48:37 EDT
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.