David Teigland writes:
> On Tue, Apr 26, 2016 at 09:57:06PM +0200, Valentin Vidic wrote:
>
>> The bug is caused by the missing braces in the expanded if
>> statement.
>>
>> Do you think we can get a new version out with this patch as the
>> fencing in 4.0.4 does not work properly due to this iss
On Tue, Apr 26, 2016 at 09:57:06PM +0200, Valentin Vidic wrote:
> The bug is caused by the missing braces in the expanded if
> statement.
>
> Do you think we can get a new version out with this patch as the
> fencing in 4.0.4 does not work properly due to this issue?
Thanks for seeing that, I'll
On Fri, Jan 22, 2016 at 07:57:52PM +0300, Vladislav Bogdanov wrote:
> Tried reverting this one and a51b2bb ("If an error occurs unlink the
> lock file and exit with status 1") one-by-one and both together, the
> same result.
>
> So problem seems to be somewhere deeper.
I've got the same fencing
22.01.2016 19:28, David Teigland wrote:
On Fri, Jan 22, 2016 at 06:59:25PM +0300, Vladislav Bogdanov wrote:
Hi David, list,
recently I tried to upgrade dlm from 4.0.2 to 4.0.4 and found that it
no longer handles fencing of a remote node initiated by other cluster
components.
First I noticed th
On Fri, Jan 22, 2016 at 06:59:25PM +0300, Vladislav Bogdanov wrote:
> Hi David, list,
>
> recently I tried to upgrade dlm from 4.0.2 to 4.0.4 and found that it
> no longer handles fencing of a remote node initiated by other cluster
> components.
> First I noticed that during valid fencing due to
Hi David, list,
recently I tried to upgrade dlm from 4.0.2 to 4.0.4 and found that it
no longer handles fencing of a remote node initiated by other cluster
components.
First I noticed that during valid fencing due to resource stop failure,
but it is easily reproduced with 'crm node fence XXX'.
I
