Red Hat Bugzilla – Bug 459160
UI support: fenced config option to skip nodes with undefined fencing
Last modified: 2009-04-16 18:44:30 EDT
+++ This bug was initially created as a clone of Bug #459127 +++
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
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
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from email@example.com on 2008-08-14 12:02:23 EDT ---
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
--- Additional comment from firstname.lastname@example.org on 2008-08-14 12:48:14 EDT ---
Created an attachment (id=314331)
very simple patch (untested)
--- Additional comment from email@example.com on 2008-08-14 13:00:00 EDT ---
patch in comment 2 left out a couple of key bits, ignore it
--- Additional comment from firstname.lastname@example.org on 2008-08-14 13:14:50 EDT ---
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.
--- Additional comment from email@example.com on 2008-08-14 14:02:21 EDT ---
Created an attachment (id=314338)
Adds a couple missing bits from previous patch.
Nodes with no methods are skipped in startup fencing only.
The skip_undefined setting is only one small piece of the puzzle
when setting up an asymmetric config:
I suspect that full UI support for these configs would be a pretty
big undertaking. And probably unnecessary unless we're planning
to promote this kind of configuration more generally.
The assymetric config options are not in any way official, promoted or
tested. As such, they should remain hidden in the code for people who
want to do unofficial experimentation. Exposing them in a UI would
not be appropriate unless they become official and tested features.