[Pacemaker] crm resource move doesn't move the resource
Pavlos Parissis
pavlos.parissis at gmail.com
Wed Sep 29 07:55:14 UTC 2010
On 28 September 2010 15:09, Pavlos Parissis <pavlos.parissis at gmail.com>wrote:
> Hi,
>
>
> When I issue "crm resource move pbx_service_01 node-0N" it moves this
> resource group but the fs_01 resource is not started because drbd_01 is
> still running on other node and it is not moved as well tonode-0N, even I
> have colocation constraints.
> I am pretty sure that I have that working before, but I can't figure why it
> doesn't work anymore.
> The resource pbx_service_01 and drbd_01 are moved to another node in case
> of failure, but for some reason not manually.
>
> Can you see in my conf where it could be the problem? I have already spent
> some time and I think I can't see the obvious anymore:-(
>
> [...snip ...]
Just to that this issue is applicable only for one of the resource group,
even the conf is the same for both of them!
So, after hours of running the same test again and again, and reading 100000
lines of logs (BTW it seams that they say in a clear way why certain things
happen) I decided to recreate the drbd_01 and ms-drbd_01 resource and adjust
the order constraints
before it was like this
order fs_01-after-drbd_01 inf: ms-drbd_01:promote fs_01:start
order fs_02-after-drbd_02 inf: ms-drbd_02:promote fs_02:start
order pbx_01-after-fs_01 inf: fs_01 pbx_01
order pbx_01-after-ip_01 inf: ip_01 pbx_01
order pbx_02-after-fs_02 inf: fs_02 pbx_02
order pbx_02-after-ip_02 inf: ip_02 pbx_02
and now like this
order fs_02-after-drbd_02 inf: ms-drbd_02:promote fs_02:start
order pbx_02-after-fs_02 inf: fs_02 pbx_02
order pbx_02-after-ip_02 inf: ip_02 pbx_02
order pbx_service_01-after-drbd_01 inf: ms-drbd_01:promote
pbx_service_01:start*
*
as you can see no major changes.
The end result is that now every time I issue "crm resource move
pbx_service_01 node-0N" the drbd_01 is promoted on that node as well and the
whole resource group is started! So, issue is solved but I don't like it for
the very simple reason, I don't why it didn't work, and that scares me!
Cheers,
Pavlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100929/a0d160ef/attachment-0002.htm>
More information about the Pacemaker
mailing list