Re: [ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Ken Gaillot
On 05/12/2016 02:56 AM, Ulrich Windl wrote: > Hi! > > I have a question regarding an RA written by myself and pacemaker > 1.1.12-f47ea56 (SLES11 SP4): > > During "probe" all resources' "monitor" actions are executed (regardless of > any ordering constraints). Therefore my RA considers a

Re: [ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Kristoffer Grönlund
Ulrich Windl writes: > Should I mess with ocf_is_probe? That's probably the easiest way forward. Quite a few RAs have solved the problem in exactly that way (see the vmware RA for example). Cheers, Kristoffer > > Regards, > Ulrich > > > >

[ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Ulrich Windl
Hi! I have a question regarding an RA written by myself and pacemaker 1.1.12-f47ea56 (SLES11 SP4): During "probe" all resources' "monitor" actions are executed (regardless of any ordering constraints). Therefore my RA considers a parameter as invalid ("file does not exist") (the file will be