[Pacemaker] Remove a "ghost" node

[Andrew Beekhof]

On 15 Nov 2013, at 2:28 pm, Sean Lutner <sean at rentul.net> wrote:

>>>> Yes the varnish resources are in a group which is then cloned.
>>> 
>>> -EDONTDOTHAT
>>> 
>>> You cant refer to the things inside a clone.
>>> 1.1.8 will have just been ignoring those constraints.
>> 
>> So the implicit order and colocation constraints in a group and clone will take care of those?
>> 
>> Which means remove the constraints and retry the upgrade?

No, it means rewrite them to refer to the clone - whatever is the outer most container. 

> 
> I was able to get the upgrade done. I also had to upgrade the libqb package. I know that's been mentioned in other threads, but I think that should either be a dependency of pacemaker or explicitly documented.

libqb is a dependancy, just not a versioned one.
We should probably change that next time.

> 
> Second order of business is that failover is no longer working as expected. Because the order and colocation constraints are gone, if one of the varnish resources fails, the EIP resource does not move to the other node like it used to.
> 
> Is there a way I can create or re-create that behavior?

See above :)

> 
> The resource group EIP-AND_VARNISH has the three varnish services and is then cloned so running on both nodes. If any of them fail I want the EIP resource to move to the other node.
> 
> Any advice for doing this?
> 
> Thanks

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131118/a1133637/attachment-0003.sig>