Date: Mon May 19 10:55:54 CEST 2008
By: hb_report -u root -f May 19 10:50:52 -t May 19 10:52:03 /tmp/report1
Subject: [short problem description]
Severity: [choose one] enhancement minor normal major critical blocking
Component: [choose one] CRM LRM CCM RA fencing heartbeat comm GUI tools other

Detailed description:
---
Hi,

I set the resource_stickiness to INFINITY so resources don't fail-back
randomly.  One test scenario (on node ldirector2) in which I damage the
resource configuration (ldirectord) so it can't start up, the node get's
STONITHed as expected and the resources fail over.

However, when it comes up again and heartbeat is started, the monitor operation
fails on ldirector2 and get's STONITHed again. After the stonith, the resource
does not fail over anymore.

I suspect my monitor to be misconfigured. The hb_report is between 10:50:52 and
10:52:03 where I started up the ldirector2 node.
---

Common system info found:
Heartbeat version: 2.1.3-0.9
CRM Version: 2.1.3 (node: a3184d5240c6e7032aef9cce6e5b7752ded544b3)
Platform: Linux
Kernel release: 2.6.16.60-0.17-default
Architecture: i686
Distribution: Description:	SUSE Linux Enterprise Server 10 (i586)
