[Pacemaker] Time-based resource stickiness not working cleanly

[Jake Smith]

----- Original Message -----
> From: "Prakash Velayutham" <Prakash.Velayutham at cchmc.org>
> To: "Jake Smith" <jsmith at argotec.com>, "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, June 27, 2012 5:39:51 PM
> Subject: Re: [Pacemaker] Time-based resource stickiness not working cleanly
> 
> Hi Jake,
> 
> On Jun 27, 2012, at 4:42 PM, Jake Smith wrote:
> 
> > ----- Original Message -----
> >> From: "Prakash Velayutham" <Prakash.Velayutham at cchmc.org>
> >> To: "The Pacemaker cluster resource manager"
> >> <pacemaker at oss.clusterlabs.org>
> >> Sent: Wednesday, June 27, 2012 4:06:39 PM
> >> Subject: Re: [Pacemaker] Time-based resource stickiness not
> >> working cleanly
> >> 
> >> I created a simple IPaddr2 resource for this testing.
> >> 
> >> 1. I can confirm that this resource (with just a location
> >> preference
> >> constraint and nothing else) does not get restarted when a node
> >> reboots. So must be something with the clone/group resources. Not
> >> sure how to debug right now.
> > 
> > Not sure but maybe something to do with interleave/ordered in the
> > clone definition?
> > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch10s02s02.html
> > 
> > You should try what Phil said and create a dummy primitive and
> > clone that then test and see if the cloned dummy exhibits the same
> > issues as the problem ones.
> 
> Yes, I will, in a short while. Will report back how it goes.
> 
> > 
> >> 2. I have a time-based rule which prevents any resource in the
> >> cluster from going back to the preferred node between 7am and 3pm,
> >> monday through friday.
> >> 	I can confirm that in my setting this does not work reliably.
> >> 		The resource fails over to the non-preferred node, but stays
> >> 		there
> >> 		even if the current time is outside of the core business hours.
> >> 		If I manually stop and start the resource, then it respects the
> >> 		location preference and goes to the preferred node.
> >> 		I have the cluster-recheck-interval set to 1min.
> > 
> > I didn't see/look at your config but that sounds like a score
> > problem between stickiness/clone score/rule value.
> 
> If you have a working time-based rule at your site that you are
> willing to share (after deidentifying that is), that will be much
> appreciated.
> 

Sorry for the long delay with an answer!

Unfortunately no I don't have/use time based rules yet so I can't offer any better assistance

Jake