HA state unavailable, though working
Stork 1.4.0 is showing both Kea 2.1.7 dhcp4 servers in HA+MT with state unavailable. Actually, there are both working fine, as Stork server is.
To Reproduce Steps to reproduce the behaviour:
- Run Kea 2.1.7 in High-availability hot-standby + Multi Threading on two machines, Stork server running on machine 1
- Restart both machine (to be sure to be sure)
- Witness that after every daemon has started, and the logs are showing a correct HA state (machine 1 = primary and OK, machine 2 in hot-standby)
- Make some tests (stop one dhcp4 service, validate that clients still get served, restart, witness a correct chat between both nodes)
- During all this, the stork web GUI dashboard (very first page after login) is showing : "HA state unavailable"
When clicking on the "unavailable" clickable link, it leads me to a page where everything is green, OK, correct, valid as it can be.
Expected behaviour The dashboard show report a situation as happy as the reality is when looking at the details pages, or in the logs, or in the currently running services.
Environment:
- Kea version: 2.1.7
- Stork agent + server : 1.4.0
- OS: Debian 11 bullseye
Contacting you
Edited by Nicolas E