Re: [ClusterLabs] CIB: op-status=4 ?

Thanks, your explanation is very helpful considering that it happens rarely and only on the first boot after VMs are created. On Mon, May 22, 2017 at 9:34 PM, Ken Gaillot wrote: > On 05/19/2017 02:03 PM, Radoslaw Garbacz wrote: > > Hi, > > > > I have some more information

Re: [ClusterLabs] CIB: op-status=4 ?

On 05/19/2017 02:03 PM, Radoslaw Garbacz wrote: > Hi, > > I have some more information regarding this issue (pacemaker debug logs). > > Firstly, I have not mentioned probably important facts: > 1) this happen rarely > 2) this happen only on first boot > 3) turning on debug in corosync/pacemaker

Re: [ClusterLabs] CIB: op-status=4 ?

Hi, I have some more information regarding this issue (pacemaker debug logs). Firstly, I have not mentioned probably important facts: 1) this happen rarely 2) this happen only on first boot 3) turning on debug in corosync/pacemaker significantly reduced frequency of this happening, i.e. without

Re: [ClusterLabs] CIB: op-status=4 ?

On 05/17/2017 06:10 PM, Radoslaw Garbacz wrote: > Hi, > > I have a question regarding ' 'op-status > attribute getting value 4. > > In my case I have a strange behavior, when resources get those "monitor" > operation entries in the CIB with op-status=4, and they do not seem to > be called

[ClusterLabs] CIB: op-status=4 ?

Hi, I have a question regarding ' 'op-status attribute getting value 4. In my case I have a strange behavior, when resources get those "monitor" operation entries in the CIB with op-status=4, and they do not seem to be called (exec-time=0). What does 'op-status' = 4 mean? I would appreciate