<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="2" face="Courier 10 Pitch">hi guys.<br>
<br>
A cluster thinks the resource is up:<br>
...<br>
* HA-10-1-1-80 (ocf:heartbeat:IPaddr2): Started ubusrv3
(disabled)<br>
..<br>
while it is not the case. What might it mean?<br>
Config is simple:<br>
-> $ pcs resource config HA-10-1-1-80<br>
Resource: HA-10-1-1-80 (class=ocf provider=heartbeat
type=IPaddr2)<br>
Attributes: cidr_netmask=24 ip=10.1.1.80<br>
Meta Attrs: failure-timeout=20s target-role=Stopped<br>
Operations: monitor interval=10s timeout=20s
(HA-10-1-1-80-monitor-interval-10s)<br>
start interval=0s timeout=20s
(HA-10-1-1-80-start-interval-0s)<br>
stop interval=0s timeout=20s
(HA-10-1-1-80-stop-interval-0s)<br>
<br>
I expected, well.. cluster to behave.<br>
This results in a trouble - because of that exactly I think - for
when resource is re-enabled then that IP/resource is not
instantiated.<br>
Is its monitor not working?<br>
Is there a way to "harden" cluster perhaps via resource config?<br>
cluster is Ubuntu VM boxes.<br>
<br>
many thanks, L.<br>
<br>
</font>
</body>
</html>