[ClusterLabs] Wait until resource is really ready before moving clusterip

[Kristoffer Grönlund]

Joakim Hansson <joakim.hansson87 at gmail.com> writes:

>
> When adding the Delay RA it starts throwing a bunch of errors and the
> cluster starts fencing the nodes one by one.
>
> The error's I get with "pcs status":
>
> Failed Actions:
> * Delay_monitor_0 on node03 'unknown error' (1): call=51, status=Timed Out,
> exit
> reason='none',
>     last-rc-change='Thu Jan 14 13:30:14 2016', queued=0ms, exec=30002ms
> * Delay_monitor_0 on node01 'unknown error' (1): call=53, status=Timed Out,
> exit
> reason='none',
>     last-rc-change='Thu Jan 14 13:30:14 2016', queued=0ms, exec=30002ms
> * Delay_monitor_0 on node02 'unknown error' (1): call=51, status=Timed Out,
> exit
> reason='none',
>     last-rc-change='Thu Jan 14 13:30:14 2016', queued=0ms, exec=30006ms
>
> and in the /var/log/pacemaker.log:
>
> https://github.com/apepojken/pacemaker-errors/blob/master/ocf:heartbeat:Delay
>
> I added the Delay RA with:
>
> pcs resource create Delay ocf:heartbeat:Delay \
> startdelay="120" meta target-role=Started \
> op start timeout="180"
>
> and my config looks like this:
>
> https://github.com/apepojken/pacemaker/blob/master/Config
>
> Am I missing something obvious here?

Hi,

It looks like you have a monitor operation configured for the Delay
resource, but you haven't set the mondelay parameter. But either way,
there is no reason to monitor the Delay resource, so remove that. Same
thing for the stop operation, just remove it.

I'm guessing pcs adds these by default.

Cheers,
Kristoffer

>
> Thanks again for all the help so far!
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-- 
// Kristoffer Grönlund
// kgronlund at suse.com