[ClusterLabs] Unexpected resource restart

[Valentin Vidic]

On Wed, Jan 16, 2019 at 12:28:59PM +0100, Valentin Vidic wrote:
> When node2 is set to standby resource stop running there.  However when
> node2 is brought back online, it causes the resources on node1 to stop
> and than start again which is a bit unexpected?
> 
> Maybe the dependency between the common storage group and the upper
> gfs2/ocfs2 groups could be written in some other way to prevent this
> resource restart?

This is what pacemaker says about the resource restarts:

Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      dlm:1           (         node2 )  
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      lockd:1         (         node2 )  
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Restart    gfs2-lvm:0      (         node1 )   due to required storage-clone running
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Restart    gfs2-fs:0       (         node1 )   due to required gfs2-lvm:0 start
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      gfs2-lvm:1      (         node2 )  
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      gfs2-fs:1       (         node2 )  
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Restart    ocfs2-lvm:0     (         node1 )   due to required storage-clone running
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Restart    ocfs2-fs:0      (         node1 )   due to required ocfs2-lvm:0 start
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      ocfs2-lvm:1     (         node2 )  
Jan 16 11:19:08 node1 pacemaker-schedulerd[713]:  notice:  * Start      ocfs2-fs:1      (         node2 )  

-- 
Valentin