[Pacemaker] on-fail not effective as of Pacemaker 1.1

David Vossel dvossel at redhat.com
Thu Feb 7 15:42:09 UTC 2013



----- Original Message -----
> From: "James Guthrie" <jag at open.ch>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Thursday, February 7, 2013 7:11:25 AM
> Subject: [Pacemaker] on-fail not effective as of Pacemaker 1.1
> 
> 
> Hi,
> 
> 
> this is a followup on this message thread:
> http://www.gossamer-threads.com/lists/linuxha/pacemaker/79252
> 
> 
> In that thread, Andrew acknowledges the behaviour as buggy, David
> opens a bug report which he was intending to investigate. The link
> is no longer active leading me to believe that it may have been lost
> when the bug reporting system died.
> 
> 
> I was able to reproduce the same behaviour with 1.1.8, which leads me
> to believe that this bug wasn't fixed.

Here's the commit.  I'm not sure what happened to the issue report.

commit 54266cb5095c68a3afac0be9be93718435352d47
Author: David Vossel <dvossel at redhat.com>
Date:   Thu Apr 12 12:26:30 2012 -0500

    Medium: pengine: cl#5058 - Fixes issue with on-fail option on operation being ignored.
    
    When the rc-code held in the lrm last failure status field refers to the
    action represented by the operation and operation_key values, not the
    operation and failure id values. When operation_key is present in the
    operation status, use that value over the id for the action key.


-- Vossel

> Regards,
> James
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 




More information about the Pacemaker mailing list