Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

Just to close the loop on this issue, discussions with Redhat have confirmed that this behavior is as designed, that all membership changes must first be realized by the Corosync layer. So the full trajectory of a STONITH action in response to, for example, a failed stop operation looks like: crm

Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

Thanks very much for your reply Ken. Unfortunately, the same delay happens when the DC is not the node that's being STONITHed. In either case, the failure looks the same to me: the stonithd instance that does the STONITH operation does not pass back the result to the original stonithd, so remote_o

Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

On 03/13/2017 10:43 PM, Chris Walker wrote: > Thanks for your reply Digimer. > > On Mon, Mar 13, 2017 at 1:35 PM, Digimer > wrote: > > On 13/03/17 12:07 PM, Chris Walker wrote: > > Hello, > > > > On our two-node EL7 cluster (pacemaker: 1.1.15-11.el7_3.4;

Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

Thanks for your reply Digimer. On Mon, Mar 13, 2017 at 1:35 PM, Digimer wrote: > On 13/03/17 12:07 PM, Chris Walker wrote: > > Hello, > > > > On our two-node EL7 cluster (pacemaker: 1.1.15-11.el7_3.4; corosync: > > 2.4.0-4; libqb: 1.0-1), > > it looks like successful STONITH operations are not c

Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

On 13/03/17 12:07 PM, Chris Walker wrote: > Hello, > > On our two-node EL7 cluster (pacemaker: 1.1.15-11.el7_3.4; corosync: > 2.4.0-4; libqb: 1.0-1), > it looks like successful STONITH operations are not communicated from > stonith-ng back to theinitiator (in this case, crmd) until the STONITHed >

[ClusterLabs] STONITH not communicated back to initiator until token expires

Hello, On our two-node EL7 cluster (pacemaker: 1.1.15-11.el7_3.4; corosync: 2.4.0-4; libqb: 1.0-1), it looks like successful STONITH operations are not communicated from stonith-ng back to theinitiator (in this case, crmd) until the STONITHed node is removed from the cluster when Corosync notices