KEA DHCP-server sometimes could be in the race condition when an interface is not in the UP state.
The server tries to open the socket 5 times with an interval of 5 seconds, then just starts as it is.
In this case, users cannot get leases from the interface, which was in the DOWN state before starting KEA, but it is now in the UP state.
I cannot get configuration from the real users with this issue, and there is no set of commands to reproduce.
Let's assume that this bug exists, so the first that could help is increasing the maximal number of retries that Kea makes to open a socket.
I propose to increase service-sockets-max-retries from 5 to 60
Some related links:
https://arran.physics.gla.ac.uk/wp/igr-it/2024/01/10/kea-dhcp-service-failing-to-open-network-socket-on-boot/
https://gitlab.isc.org/isc-projects/kea/-/issues/3188
https://gitlab.isc.org/isc-projects/kea/-/issues/2776
https://gitlab.isc.org/isc-projects/kea/-/issues/1084