[ClusterLabs] Old Pacemaker bug avoiding

Ken Gaillot kgaillot at redhat.com
Mon Nov 26 15:50:22 EST 2018

On Thu, 2018-11-22 at 11:24 +0700, Субботин Никита Андреевич wrote:
> Hello,
> I use the old Pacemaker version (1.1.7), and I'm dealing with bug 
> cl#5072 (monitor op stopping after rsc promotion), which was fixed
> in 
> the next Pacemaker version (1.1.8). But due to some reasons I have
> to 
> use this and only this version of Pacemaker. Is there any way to
> avoid 
> this bug? I have two ideas, but none of them are perfect:
> 1) monitor Pacemaker logs via cron to identify the resource stop and 
> cleanup the resource via crm
> 2) monitor the resource itself via cron and cleanup the resource via
> crm
> I would appreciate any help

I don't know if a cleanup would help.

My first thought is to set the target-role to Slave, then back to
Master. This would of course leave the cluster with no master for a
period of time, but I think it would reschedule the monitors.
Ken Gaillot <kgaillot at redhat.com>

More information about the Users mailing list