I'm using pacemaker 1.1.8 and I don't see stonith resources moving away
from AWOL hosts like I thought I did with 1.1.7. So I guess the first
thing to do is clear up what is supposed to happen.
If I have a single stonith resource for a cluster and it's running on
node A and then node A goes
On 2013-04-30T10:55:41, Brian J. Murrell br...@interlinx.bc.ca wrote:
From what I think I know of pacemaker, pacemaker wants to be able to
stonith that AWOL node before moving any resources away from it since
starting a resource on a new node while the state of the AWOL node is
unknown is
On 13-04-30 11:13 AM, Lars Marowsky-Bree wrote:
Pacemaker 1.1.8's stonith/fencing subsystem directly ties into the CIB,
and will complete the fencing request even if the fencing/stonith
resource is not instantiated on the node yet.
But clearly that's not happening here.
(There's a bug in
On 01/05/2013, at 1:28 AM, Brian J. Murrell br...@interlinx.bc.ca wrote:
On 13-04-30 11:13 AM, Lars Marowsky-Bree wrote:
Pacemaker 1.1.8's stonith/fencing subsystem directly ties into the CIB,
and will complete the fencing request even if the fencing/stonith
resource is not instantiated on
