Red Hat Bugzilla – Bug 158891
fenced asks for node info which may not exist in all cases during startup
Last modified: 2009-04-16 16:09:22 EDT
Description of problem:
Fenced was asking for this from ccsd in order to see if the local node
name was present in the cluster configuration:
Unfortunately, because there were no children of that XML node (no
fencing configured), ccsd was crashing (this is a separate issue).
That query doesn't return data in the cases where the local node doesn't
have fencing (which, I know is an unsupported config), but fenced should
be able to fence other nodes even if the local node is running in an
unsupported configuration. So, it should have been asking for something
which will exist in all fencing cases:
Version-Release number of selected component (if applicable):
-RHEL4U1 -RHEL4 -RHEL4
How reproducible: 100%
Steps to Reproduce:
1. Create configuration with no fencing specified for a node.
2. Start fenced.
Fenced incorrectly determines that the local node doesn't exist in cluster.conf
This fix is dependent on a fix to ccsd which prevents it from crashing in this case.
Created attachment 114874 [details]
Adding ccs bug. Without the fix to ccsd, fenced will produce the error anyway
(because ccsd will crash with SIGSEGV).
Patches in CVS