Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-02-05 Thread Bogdan Dobrelya
On 04.02.2016 15:43, Bogdan Dobrelya wrote: > Hello. > Regarding the original issue, good news are the resource-agents > ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0] > after the fix [1] done. The bad news are that "self-forking" monitors > issue seems remaining for the

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-02-04 Thread Bogdan Dobrelya
Hello. Regarding the original issue, good news are the resource-agents ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0] after the fix [1] done. The bad news are that "self-forking" monitors issue seems remaining for the rabbitmq OCF RA [2], and I can reproduce it for another

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-06 Thread Keisuke MORI
Hi, 2016-01-06 22:57 GMT+09:00 Jan Pokorný : > Hello , > > On 04/01/16 17:33 +0100, Bogdan Dobrelya wrote: >> Note, that it seems the very import action causes the issue, not the >> ocf_run or ocf_log code itself. >> >> [0]

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-04 Thread Ken Gaillot
On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote: > On 04.01.2016 15:50, Bogdan Dobrelya wrote: >> So far so bad. >> I made a dummy OCF script [0] to simulate an example >> promote/demote/notify failure mode for a multistate clone resource which >> is very similar to the one I reported originally.

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-04 Thread Bogdan Dobrelya
On 04.01.2016 16:36, Ken Gaillot wrote: > On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote: >> On 04.01.2016 15:50, Bogdan Dobrelya wrote: >>> So far so bad. >>> I made a dummy OCF script [0] to simulate an example >>> promote/demote/notify failure mode for a multistate clone resource which >>> is

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-04 Thread Bogdan Dobrelya
On 04.01.2016 15:50, Bogdan Dobrelya wrote: > So far so bad. > I made a dummy OCF script [0] to simulate an example > promote/demote/notify failure mode for a multistate clone resource which > is very similar to the one I reported originally. And the test to > reproduce my case with the dummy is:

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-04 Thread Dejan Muhamedagic
Hi, On Mon, Jan 04, 2016 at 04:52:43PM +0100, Bogdan Dobrelya wrote: > On 04.01.2016 16:36, Ken Gaillot wrote: > > On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote: > >> On 04.01.2016 15:50, Bogdan Dobrelya wrote: [...] > >> Also note, that lrmd spawns *many* monitors like: > >> root 6495 0.0

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2016-01-01 Thread Vladislav Bogdanov
31.12.2015 15:33:45 CET, Bogdan Dobrelya wrote: >On 31.12.2015 14:48, Vladislav Bogdanov wrote: >> blackbox tracing inside pacemaker, USR1, USR2 and TRAP signals iirc, >quick google search should point you to Andrew's blog with all >information about that feature. >> Next,

Re: [ClusterLabs] [OCF] Pacemaker reports a multi-state clone resource instance as running while it is not in fact

2015-12-31 Thread Vladislav Bogdanov
31.12.2015 12:57:45 CET, Bogdan Dobrelya wrote: >Hello. >I've been hopelessly fighting a bug [0] in the custom OCF agent of Fuel >for OpenStack project. It is related to the destructive test case when >one node of 3 or 5 total goes down and then back. The bug itself is