[Pacemaker] crm resource move doesn't move the resource

[Pavlos Parissis]

On 11 October 2010 11:16, Pavlos Parissis <pavlos.parissis at gmail.com> wrote:
> On 8 October 2010 09:29, Andrew Beekhof <andrew at beekhof.net> wrote:
>> On Fri, Oct 8, 2010 at 8:34 AM, Pavlos Parissis
>> <pavlos.parissis at gmail.com> wrote:
>>> On 8 October 2010 08:29, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>> On Thu, Oct 7, 2010 at 9:58 PM, Pavlos Parissis
>>>> <pavlos.parissis at gmail.com> wrote:
>>>>>
>>>>>
>>>>> On 7 October 2010 09:01, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>>>>
>>>>>> On Sat, Oct 2, 2010 at 6:31 PM, Pavlos Parissis
>>>>>> <pavlos.parissis at gmail.com> wrote:
>>>>>> > Hi,
>>>>>> >
>>>>>> > I am having again the same issue, in a different set of 3 nodes. When I
>>>>>> > try
>>>>>> > to failover manually the resource group on the standby node, the ms-drbd
>>>>>> > resource is not moved as well and as a result the resource group is not
>>>>>> > fully started, only the ip resource is started.
>>>>>> > Any ideas why I am having this issue?
>>>>>>
>>>>>> I think its a bug that was fixed recently.  Could you try the latest
>>>>>> from code Mercurial?
>>>>>
>>>>> 1.1 or 1.2 branch?
>>>>
>>>> 1.1
>>>>
>>> to save time on compiling stuff I want to use the available rpms on
>>> 1.1.3 version from rpm-next repo.
>>> But before I go and recreate the scenario, which means rebuild 3
>>> nodes, I would like to know if this bug is fixed in 1.1.3
>>
>> As I said, I believe so.
>
> I recreated the 3 node cluster and I didn't face that issue, but I am
> going to keep an eye on it for few days and even rerun the whole
> scenario (recreate 3 node cluster ...) just to be very sure. If I
> don't the see it again I will also close the bug report
>
> Thanks,
> Pavlos
>


I recreated the 3-node cluster using 1.1.3 version just see if it is
solved, but the issue appeared again.
So, Andrew the issue is not solved in 1.1.3. I am going to update the
bug report accordingly.

Cheers,
Pavlos