On Tue, Dec 18, 2012 at 4:24 PM, pavan tc wrote:
> [..]
>
>
>> The idea is to make sure that stop does not fail when the underlying
>>
>> > resource goes away.
>> > (Otherwise I see that the resource gets to an unmanaged state)
>> > Also, the expectation is that when the resource comes back, it jo
[..]
> The idea is to make sure that stop does not fail when the underlying
> > resource goes away.
> > (Otherwise I see that the resource gets to an unmanaged state)
> > Also, the expectation is that when the resource comes back, it joins the
> > cluster without much fuss.
> >
> > What I see is
On Fri, Dec 14, 2012 at 9:32 PM, pavan tc wrote:
> Hi,
>
> I have structured my multi-state resource agent as below when the underlying
> resource becomes unavailable for some reason:
>
> monitor()
> {
> state=get_primitive_resource_state()
>
> ...
> ...
> if ($state == unavailable
Hi,
I have structured my multi-state resource agent as below when the
underlying resource becomes unavailable for some reason:
monitor()
{
state=get_primitive_resource_state()
...
...
if ($state == unavailable)
return $OCF_NOT_RUNNING
...
...
}
stop()
{
monit
