On Mon, Dec 4, 2023 at 1:21 AM lejeczek via Users <users@clusterlabs.org> wrote: > > hi guys. > > A cluster thinks the resource is up: > ... > * HA-10-1-1-80 (ocf:heartbeat:IPaddr2): Started ubusrv3 (disabled) > .. > while it is not the case. What might it mean? > Config is simple: > -> $ pcs resource config HA-10-1-1-80 > Resource: HA-10-1-1-80 (class=ocf provider=heartbeat type=IPaddr2) > Attributes: cidr_netmask=24 ip=10.1.1.80 > Meta Attrs: failure-timeout=20s target-role=Stopped > Operations: monitor interval=10s timeout=20s > (HA-10-1-1-80-monitor-interval-10s) > start interval=0s timeout=20s (HA-10-1-1-80-start-interval-0s) > stop interval=0s timeout=20s (HA-10-1-1-80-stop-interval-0s) > > I expected, well.. cluster to behave. > This results in a trouble - because of that exactly I think - for when > resource is re-enabled then that IP/resource is not instantiated. > Is its monitor not working? > Is there a way to "harden" cluster perhaps via resource config? > cluster is Ubuntu VM boxes.
Is the cluster in maintenance mode, or is anything similar happening (like blocked resources)? Is that IP address running on any interface right now? Normally the resource would be stopped (and I think the recurring monitor would be canceled?) when the resource is disabled... > > many thanks, L. > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
