[Linux-ha-dev] Difference between OCF_ERR_CONFIGURED and OCF_ERR_INSTALLED ?

[Serge Dubrouski]

On Fri, Jul 4, 2008 at 4:44 AM, Andrew Beekhof <beekhof at gmail.com> wrote:
> 2008/7/4 Joe Bill <pica1dilly at yahoo.com>:
>> Exatcly how does heartbeat handle OCF_ERR_CONFIGURED and OCF_ERR_INSTALLED
>> differently ?
>>
>
> >From some badly formatted and not-quite finished documentation:
>
> soft  = stop and retry
> hard  = stop and retry - current node is excluded
> fatal = stop - all nodes are excluded
>
> OCF Return Code Description     Recovery Type
> 0       Success.  The command complete successfully.  This is the expected
> result for all start, stop, promote and demote commands.        N/A
> 1       Generic "there was a problem" error code.       soft
> 2       Incorrect arguments were passed to the resource agent.  fatal
> 3       The requested action is not implemented.        hard

Doesn't look like it works like that. If you remember that discussion
about crm_resource -F, it restarts resource but doesn't exclude the
node,

> 4       The resource agent does not have sufficient privileges to complete
> the task.       hard
> 5       The requested agent or tool required by the agent is not installed.     hard
> 6       The resource's configuration is invalid.        fatal
> 7       The resource is safely stopped.  The cluster will not attempt to
> stop a resource that returns this for any action.       N/A
> 8       The resource is running in Master mode. N/A
> 9       The resource is in Master mode but has failed.  The resource will be
> demoted, stopped and then started (and possibly promoted) again.        soft
> other   Custom error code.      soft
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
>



-- 
Serge Dubrouski.