On 03/23/2016 12:01 PM, Vladislav Bogdanov wrote:
> 23.03.2016 19:52, Vladislav Bogdanov wrote:
>> 23.03.2016 19:39, Ken Gaillot wrote:
>>> On 03/23/2016 07:35 AM, Vladislav Bogdanov wrote:
Hi!
It seems like atomic attrd in post-1.1.14 (eb89393) does not
fully clean node cache a
23.03.2016 19:52, Vladislav Bogdanov wrote:
> 23.03.2016 19:39, Ken Gaillot wrote:
>> On 03/23/2016 07:35 AM, Vladislav Bogdanov wrote:
>>> Hi!
>>>
>>> It seems like atomic attrd in post-1.1.14 (eb89393) does not
>>> fully clean node cache after node is removed.
>>
>> Is this a regression? Or have
23.03.2016 19:39, Ken Gaillot wrote:
On 03/23/2016 07:35 AM, Vladislav Bogdanov wrote:
Hi!
It seems like atomic attrd in post-1.1.14 (eb89393) does not
fully clean node cache after node is removed.
Is this a regression? Or have you only tried it with this version?
Only with this one.
Af
On 03/23/2016 07:35 AM, Vladislav Bogdanov wrote:
> Hi!
>
> It seems like atomic attrd in post-1.1.14 (eb89393) does not
> fully clean node cache after node is removed.
Is this a regression? Or have you only tried it with this version?
> After our QA guys remove node wa-test-server-ha-03 from a
Hi!
It seems like atomic attrd in post-1.1.14 (eb89393) does not
fully clean node cache after node is removed.
After our QA guys remove node wa-test-server-ha-03 from a two-node cluster:
* stop pacemaker and corosync on wa-test-server-ha-03
* remove node wa-test-server-ha-03 from corosync nodelist