[ClusterLabs] ocf:pacemaker:ping works strange

[Artem]

Hi Ken,

On Mon, 11 Dec 2023 at 19:00, Ken Gaillot <kgaillot at redhat.com> wrote:

> > Question #2) I shut lustre3 VM down and leave it like that


> How did you shut it down? Outside cluster control, or with something
> like pcs resource disable?
>
> I did it outside of the cluster to simulate a failure. I turned off this
VM from vCenter. Cluster is unaware of anything behind OS.


> >   * FAKE3       (ocf::pacemaker:Dummy):  Stopped
> >   * FAKE4       (ocf::pacemaker:Dummy):  Started lustre4
> >   * Clone Set: ping-clone [ping]:
> >     * Started: [ lustre-mds1 lustre-mds2 lustre-mgs lustre1 lustre2
> > lustre4 ] << lustre3 missing
> > OK for now
> > VM boots up. pcs status:
> >   * FAKE3       (ocf::pacemaker:Dummy):  FAILED (blocked) [ lustre3
> > lustre4 ]  << what is it?
> >   * Clone Set: ping-clone [ping]:
> >     * ping      (ocf::pacemaker:ping):   FAILED lustre3 (blocked)
> > << why not started?
> >     * Started: [ lustre-mds1 lustre-mds2 lustre-mgs lustre1 lustre2
> > lustre4 ]
> > I checked server processes manually and found that lustre4 runs
> > "/usr/lib/ocf/resource.d/pacemaker/ping monitor" while lustre3
> > doesn't
> > All is according to documentation but results are strange.
> > Then I tried to add meta target-role="started" to pcs resource create
> > ping and this time ping started after node rebooted. Can I expect
> > that it was just missing from official setup documentation, and now
> > everything will work fine?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20231211/f381fec0/attachment.htm>