Hi Ken,
I managed to reproduce this on a simplified version of the cluster, and on
Pacemaker 1.1.15, 1.1.16, as well as 1.1.18-rc1
The steps to create the cluster are:
pcs property set stonith-enabled=false
pcs property set placement-strategy=balanced
pcs node utilization vm1 cpu=100
pcs node
>
> > Pending actions:
> > Action 40: sv_fencer_monitor_6 on brilxvm44
> > Action 39: sv_fencer_start_0 on brilxvm44
> > Action 38: sv_fencer_stop_0 on brilxvm43
> > Error performing operation: Timer expired
> >
> > It looks like it's waiting for the sv_fencer fencing agent to start
> > on
On Mon, 2017-10-09 at 16:37 +1000, Leon Steffens wrote:
> Hi all,
>
> We have a use case where we want to place a node into standby and
> then wait for all the resources to move off the node (and be started
> on other nodes) before continuing.
>
> In order to do this we call:
> $ pcs cluster
Hi all,
We have a use case where we want to place a node into standby and then wait
for all the resources to move off the node (and be started on other nodes)
before continuing.
In order to do this we call:
$ pcs cluster standby brilxvm45
$ crm_resource --wait --timeout 300
This works most of
