Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
If you boot a non-xen kernel w/ fence_xvmd, enabled in the cluster config, the
script returns a failure.
This isn't actually correct.
* Install a RHEL5 guest with advanced platform,
* Enable xend (chkconfig --level 2345 xend on)
* Install the current RHEL5 cluster errat for cman, and
* boot a kernel without Xen support,
...the cman init script chokes and will not start cman. This is actually not
related to fence_xvmd as originally thought.
This is consistent with the operational specification of how fence_xvmd is
started: failing to start fence_xvmd does not cause a failure of other parts of
Created attachment 154474
This patch should fix the problem. I've applied it to the HEAD and RHEL5
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
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.