Heartbeat status when both HA machines fail is still OK for primary
The issue was found during 1.1.0 sanity checks. Source
I authorized two HA machines and next used Kea Environment Simulator to kill both kea-dhcp4
daemons. Stork detects correctly that both daemons are down, but the primary server has Heartbeat status: OK
with the description "Status of the heartbeat communication with the remote server is unknown.". I think that the status shouldn't be OK.
Additionally, the Detected Failure w/HA
on Dashboard is never
for the primary server.