_check_host_status_by_crmadmin [1] is the proper safeguard.
Hostmonitor should be treated as pacemaker proxy so should run on pacemaker nodes (not remotes).
I guess this needs documenting and disabling its functionality on non-pacemaker nodes altogether.
There is no benefit to running hostmonitors on remotes, it can only result in more resource waste and less stability.
_check_ host_status_ by_crmadmin [1] is the proper safeguard.
Hostmonitor should be treated as pacemaker proxy so should run on pacemaker nodes (not remotes).
I guess this needs documenting and disabling its functionality on non-pacemaker nodes altogether.
There is no benefit to running hostmonitors on remotes, it can only result in more resource waste and less stability.
[1] https:/ /opendev. org/openstack/ masakari- monitors/ src/commit/ b02c6b6931c0256 f4ce6d7167c97eb b849ff3453/ masakarimonitor s/hostmonitor/ host_handler/ handle_ host.py# L414-L418