[Pacemaker] Time-based location constraint not working in HB 2.1.4?

[Andrew Beekhof]

Have you read the section on "Ensuring Time Based Rules Take Effect" ?

On Dec 11, 2008, at 10:23 AM, Andreas Kurz wrote:

> Hello list!
>
> I tried to get time-based location constraints working with Heartbeat
> 2.1.4.
>
> I tested with a dummy resource (including a monitor operation) and the
> rules are obeyed once when updating the cib with the new config or  
> doing
> a ptest but when waiting for the resource being moved to another node
> because of the time-based location constraint is not working.
>
>   <rsc_location id="loc_dummy_timebased" rsc="resource_dummy">
>     <rule id="prefered_loc_dummy_11-12" boolean_op="and" score="300">
>       <date_expression id="date_expr_11-12" operation="date_spec">
>         <date_spec hours="11-12" id="date_spec_11-12"/>
>       </date_expression>
>       <expression attribute="#uname" id="node1_id" operation="eq"
> value="node1"/>
>     </rule>
>     <rule id="prefered_loc_dummy_13-10" boolean_op="and" score="300">
>       <rule id="prefered_loc_ummy_13-10" boolean_op="or">
>         <date_expression id="date_expr_13-23" operation="date_spec">
>           <date_spec hours="13-23" id="date_spec_13-23"/>
>         </date_expression>
>         <date_expression id="date_expr_0-10" operation="date_spec">
>           <date_spec hours="0-10" id="date_spec_0-10"/>
>         </date_expression>
>       </rule>
>       <expression attribute="#uname" id="node2_id" operation="eq"
> value="node2"/>
>     </rule>
>   </rsc_location>
>
>
> ... default-resource-stickiness=200
>
> Any ideas? Config problem, feature, bug?
>
> thx & Regards,
> Andreas
>
> -- 
> : Andreas Kurz					
> : LINBIT | Your Way to High Availability
> : Tel +43-1-8178292-64, Fax +43-1-8178292-82
> :
> : http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
>
> This e-mail is solely for use by the intended recipient(s).  
> Information
> contained in this e-mail and its attachments may be confidential,
> privileged or copyrighted. If you are not the intended recipient you  
> are
> hereby formally notified that any use, copying, disclosure or
> distribution of the contents of this e-mail, in whole or in part, is
> prohibited. Also please notify immediately the sender by return e-mail
> and delete this e-mail from your system. Thank you for your co- 
> operation.
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker