[ClusterLabs] What happened to "crm resource migrate"?

[Strahil]

What about the constraint.
I think there is no 'crm resource unmove'  to remmove the constraint.

Best Regards,
Strahil NikolovOn Oct 15, 2019 11:52, Yan Gao <YGao at suse.com> wrote:
>
> Hi Ulrich, 
>
> On 10/15/19 10:26 AM,  Ulrich Windl  wrote: 
> > Hi! 
> > 
> > I was trying to do a "crm resource migrate" the first time in SLES 12 (the way I did in SLES11), but I got this message: 
> > # crm resource migrate prm_isr_mail1 PT10M 
> > ERROR: resource.move: No target node: Move requires either a target node or 'force' 
> > 
> > I'm surprised: In the past the mommand simply added a negative location for the node the was running (at least I think). 
> > The resource was running on the other node of a two-node cluster... 
> > 
> > Also I noticed that "migrate" no longer appears in crm's help for "resource". There's only a "move". 
> Yes, the term/sub-command "migrate" is deprecated in favor of "move", so 
> that it's consistent with "crm_resource --move ". But "migrate" is 
> supposed to still work. 
>
> > 
> > Help for "move" still says: 
> > resource# help move 
> > Move a resource to another node 
> > 
> > Move a resource away from its current location. 
> Looks like an issue in the version of crmsh. 
>
> Xin, could you please take a look? 
>
> "crm_resource --move -r <rsc>" is allowed to run without being specified 
> a node. 
>
> Regards, 
>    Yan 
> _______________________________________________ 
> Manage your subscription: 
> https://lists.clusterlabs.org/mailman/listinfo/users 
>
> ClusterLabs home: https://www.clusterlabs.org/