On 19 Apr 2013, at 14:48, Florian Crouzat <[email protected]> wrote:
> Well, you kinda answered this when you mentioned "crm_resource -U".
> You should use "unmove" instead of "move". Unmove will remove the
> location constraint where move will create a new one.
Thanks, that sounds much better - but it has a slightly annoying effect. I
normally have a location rule like this:
location cli-prefer-ip3 ip3 rule $id="cli-prefer-rule-ip3" inf: #uname eq proxy1
When I issue a move, it gets removed and replaced with:
location cli-standby-ip3 ip3 \
rule $id="cli-standby-rule-ip3" -inf: #uname eq proxy1
When I unmove, it deletes that location rule, but because the preference rule
has been removed, it doesn't result in the ip moving back because there is no
longer any preferred node, so no incentive for it to do so. This seems to
rather defeat the point of unmove.
Is there a move/unmove that doesn't apply location rules, but just tells the
resource to move?
Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK info@hand CRM solutions
[email protected] | http://www.synchromedia.co.uk/
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
