-
Notifications
You must be signed in to change notification settings - Fork 603
Open
Description
Hi Oyvind,
Hi All,
The following modification to IPaddr2 added a DOWN/LOWERLAYERDOWN error detection function, but when this error is detected by the monitor, it is treated as ERR_INSTALLED.
For this reason, even if the user is controlling the failure migration-threshold (0, number, INFINITY), if the monitor error is controlled by ERR_INSTALLED, an FO will occur immediately.
Some users may want to ignore the monitor failure for the IPaddr2 resource (by setting the migration-threshold to 0) and prevent the resource from FO.
Rather than ERR_INSTALLED, shouldn't NOT_RUNNING be returned and the fail-count control be left to Pacemaker's migration-thresholds (0, number, INFINITY)?
(snip)
ip_monitor() {
# TODO: Implement more elaborate monitoring like checking for
# interface health maybe via a daemon like FailSafe etc...
local ip_status=`ip_served`
ocf_log debug "monitor: $ip_status"
case $ip_status in
ok)
run_arp_sender refresh
return $OCF_SUCCESS
;;
no|down) # or DOWN
exit $OCF_NOT_RUNNING
;;
(snip)
Best Regards,
Hideo Yamauchi.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels