[Pacemaker] Designated reaction of Pacemaker to monitor-op returning rc=7 (OCF_NOT_RUNNING)

[Andrew Beekhof]

On Thu, Aug 26, 2010 at 10:42 AM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Thu, Aug 26, 2010 at 08:20:46AM +0200, Andrew Beekhof wrote:
>> On Wed, Aug 25, 2010 at 4:00 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
>> > Hi,
>> >
>> > On Tue, Aug 24, 2010 at 05:19:23PM +0200, Cnut Jansen wrote:
>> >> Hi,
>> >>
>> >> just (for now) a short question for to make sure I didn't miss anything:
>> >> What's the designated reaction of Pacemaker when a resource agents
>> >> called for monitoring a resource, which is supposed to run and thus
>> >> resulting in a return of 0 (OCF_SUCCESS), returns 7 (OCF_NOT_RUNNING)?
>> >> Shall Pacemaker's very next call be for stopping the resource or shall
>> >> it be yet another (or even several) monitorings?
>> >
>> > It should be stop,
>>
>> No, for rc=7 you wont get a stop... the RA just told us it was already
>> safely stopped.
>
> Makes sense. But here with a recent 1.1 it does a standard
> resource recovery procedure and goes through stop/start:
>
> Aug 26 10:30:06 xen-d pengine: [20465]: WARN: unpack_rsc_op: Processing failed op d2_monitor_30000 on xen-d: not running (7)
> Aug 26 10:30:06 xen-d pengine: [20465]: notice: LogActions: Recover resource d2 (Started xen-d)
> Aug 26 10:30:06 xen-d lrmd: [20463]: info: rsc:d2:154: stop
> ...

Oh. Apparently I changed that somewhere along the line and forgot.
Stupid vacations :-)