Cman is not able to start when using unfence with fence_brocade

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 6.1 - 6.5
  • fence-agents package prior to fence-agents-3.1.5-48

Issue

Cman is not starting when using unfence in cluster.conf in combination with “fence_brocade” fencedevice.
If the unfence part is commented, the cman starts with no problems at all.

Snippet of cluster.conf:

                <clusternode name="node1" nodeid="1">
                        <fence>
                                <method name="san">
                                        <device name="sanfence" port="1"/>
                                </method>
                        </fence>
                        <unfence>
                                <device action="on" name="sanfence" port="1"/>
                        </unfence>
                </clusternode>

Resolution

  • The fence_brocade accepts only following parameters for action prior to RHEL 6.6, prior to fence-agents-3.1.5-48.el6
<actions>
        <action name="enable" />
        <action name="disable" />
        <action name="status" />
        <action name="metadata" />
</actions>

If you are using action="on" the cman will not start.

  • Please use action="enable" instead action="on" to resolve this issue.

  • RHEL 6.6+ with fence-agents-3.1.5-48.el6 or greater.

the "enable" action no longer works, and should be reverted to "on". This package was re-based in 6.6 to use python, and brought in line with our standard python fence agents which use "on" and "off" as options.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments