[Pacemaker] BUG: is-managed="true" moves resources around

Lars Marowsky-Bree lmb at suse.de
Wed Dec 16 02:26:35 EST 2009


On 2009-12-15T17:37:27, Rasto Levrinc <rasto.levrinc at linbit.com> wrote:

> So I have a group with two dummy resources that are both unmanaged but
> running. The group has colocation constraint with score -INFINITY with the
> third dummy resource. The group resources are running on one node and the
> third dummy resource on the other.
> 
> So far so good.
> 
> Now I set the first resource in the group to be managed by pacemaker and
> all managed resources decide to move to the opposite nodes. This I would
> not expect. Resource stickiness is set. If I reverse the colocation
> constraint (exchange "rsc" and "with-rsc") it works ok.
> 
> xml is attached.

>     <crm_config>
>       <cluster_property_set id="cib-bootstrap-options">
>         <nvpair id="cib-bootstrap-options-default-resource-stickiness" name="default-resource-stickiness" value="100"/>
>         <nvpair id="cib-bootstrap-options-expected-quorum-votes" name="expected-quorum-votes" value="2"/>
>         <nvpair id="cib-bootstrap-options-stonith-enabled" name="stonith-enabled" value="false"/>
>       </cluster_property_set>
>     </crm_config>

That's not a full configuration, is it? Otherwise, it would have a
dc-version element and tell us which software you're actually running
;-)


Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde




More information about the Pacemaker mailing list