Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 459127

Summary: fenced config option to skip nodes with undefined fencing
Product: Red Hat Enterprise Linux 5 Reporter: David Teigland <teigland>
Component: cmanAssignee: David Teigland <teigland>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: cluster-maint, djansa, edamato, lhh, rohara
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:52:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 459160    
Attachments:
Description Flags
proposed patch
none
proposed patch none

Description David Teigland 2008-08-14 15:58:02 UTC 
Description of problem:

New fenced config option <fence_daemon skip_undefined="1"/>
would cause fenced to not attempt any fencing on nodes with
undefined fence/method/device.  Currently, fenced tries,
fails, and retries (repeatedly) to fence a node with undefined
fence/method/device, which requires an override.

The primary use for this option would be asymmetric cluster configs
(http://sources.redhat.com/cluster/wiki/asymmetric_cluster_config)
where client/small/spectator nodes do not join the fence domain
and have no fencing configured.  The problem we have is that even with
no fencing configured, and not joining the fence domain, other
nodes may attempt (and fail) to fence these client nodes during
startup fencing.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 RHEL Program Management 2008-08-14 16:02:23 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
release.
Comment 2 David Teigland 2008-08-14 16:48:14 UTC 
Created attachment 314331 [details]
proposed patch

very simple patch (untested)
Comment 3 David Teigland 2008-08-14 17:00:00 UTC 
patch in comment 2 left out a couple of key bits, ignore it
Comment 4 David Teigland 2008-08-14 17:14:50 UTC 
I think I'd like to limit the scope of skip_undefined to skip
just startup fencing of nodes with no defined methods (as shown
in the initial patch in comment 2).  The original description of
skip_undefined was more general and also applied to domain members
that failed, which is something we don't have need for.
Comment 5 David Teigland 2008-08-14 18:02:21 UTC 
Created attachment 314338 [details]
proposed patch

Adds a couple missing bits from previous patch.
Nodes with no methods are skipped in startup fencing only.
Comment 6 David Teigland 2008-08-20 20:32:05 UTC 
pushed to RHEL5 and STABLE2
Comment 9 errata-xmlrpc 2009-01-20 21:52:16 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-0189.html