[Pacemaker] making resource managed

Vadim S. Khondar v.khondar at o3.ua
Fri Nov 12 09:47:16 UTC 2010


У ср, 2010-11-10 у 09:03 +0100, Andrew Beekhof пише:
> On Tue, Nov 9, 2010 at 2:14 PM, Vadim S. Khondar <v.khondar at o3.ua> wrote:
> > У вт, 2010-11-09 у 09:49 +0100, Andrew Beekhof пише:
> >> being unmanaged is a side-effect of a) the resource failing to stop
> >> and b) no fencing being configured
> >> once you've fixed the error, run crm resource cleanup as misch suggested
> >>
> >
> > I understand that.
> > However, for example, in situation when VPS fails to start (not to stop)
> 
> Its failing to stop too:
> 
> ca_stop_0 (node=ha-3, call=49, rc=1, status=complete): unknown error
>    ^^^^^^^^

> 
> Possibly an ordering constraint.  Otherwise, no idea.
> Depends on how your resource agent works.

No ordering constraints explicitly listed in configuration.
:(

Will try with moving to v1.1.

-- 
Vadim S. Khondar

v.khondar at o3.ua





More information about the Pacemaker mailing list