Linux Heartbeat bladehpi resource agent fails

This document (7001102) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 Service Pack 2

Situation

1. Setup/environment

Operating System
- SuSE Linux Enterprise Server 10 SP2 (x86_64)

2. Symptom
bladehpi resource agent fails.

3. Behavior

The bladehpi clone set starts but goes unmanaged after failing monitor and then stop.

============
Current DC: node2 (78d213f6-a520-4a87-88e0-78016053c161)
2 Nodes configured.
4 Resources configured.
============

Node: node1 (92384e33-e7c9-42c7-87b8-2012f032f434): online
Node: node2 (78d213f6-a520-4a87-88e0-78016053c161): online

Clone Set: stonithcloneset
    stonithclone:0    (stonith:bladehpi):    Started node1 (unmanaged) FAILED
    stonithclone:1    (stonith:bladehpi):    Started node2 (unmanaged) FAILED
Clone Set: evmscloneset
    evmsclone:0    (ocf::heartbeat:EvmsSCC):    Started node1
    evmsclone:1    (ocf::heartbeat:EvmsSCC):    Started node2
Clone Set: imagecloneset
    imageclone:0    (ocf::heartbeat:Filesystem):    Started node1
    imageclone:1    (ocf::heartbeat:Filesystem):    Started node2
Clone Set: configcloneset
    configclone:0    (ocf::heartbeat:Filesystem):    Started node1
    configclone:1    (ocf::heartbeat:Filesystem):    Started node2

Failed actions:
    stonithclone:1_stop_0 (node=node2, call=17, rc=-2): Timed Out
    stonithclone:0_stop_0 (node=node1, call=17, rc=-2): Timed Out

Resolution

A new bladehpi plugin has has been released on January 2009. Make sure you are using the current packages.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.