Re: [ClusterLabs] crm_resource --wait

Thanks for the update Ken! From: Ken Gaillot Sent: Saturday, 21 October 2017 7:06 AM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] crm_resource --wait I've narrowed down the cause. When the "standby" transition completes, vm

Re: [ClusterLabs] crm_resource --wait

I've narrowed down the cause. When the "standby" transition completes, vm2 has more remaining utilization capacity than vm1, so the cluster wants to run sv-fencer there. That should be taken into account in the same transition, but it isn't, so a second transition is needed to make it happen.

Re: [ClusterLabs] crm_resource --wait

I've attached two files: 314 = after standby step 315 = after resource update On Wed, Oct 11, 2017 at 12:22 AM, Ken Gaillot wrote: > On Tue, 2017-10-10 at 15:19 +1000, Leon Steffens wrote: > > Hi Ken, > > > > I managed to reproduce this on a simplified version of the

Re: [ClusterLabs] crm_resource --wait

On Tue, 2017-10-10 at 15:19 +1000, Leon Steffens wrote: > 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

Re: [ClusterLabs] crm_resource --wait

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

Re: [ClusterLabs] crm_resource --wait

> > > 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

Re: [ClusterLabs] crm_resource --wait

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

[ClusterLabs] crm_resource --wait

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