The „disabled“ makes me wonder.
From: Users <users-boun...@clusterlabs.org> On Behalf Of lejeczek via Users
Sent: Monday, December 4, 2023 10:21 AM
To: users@clusterlabs.org
Cc: lejeczek <pelj...@yahoo.co.uk>
Subject: [EXT] [ClusterLabs] IPaddr2 Started (disabled) ?
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.
many thanks, L.
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
