[stork-users] HA-status unavailable
Andrey Kostin
ankost at podolsk.ru
Mon Feb 26 15:53:15 UTC 2024
Slawek Figiel писал(а) 2024-02-26 10:03:
> Hello Andrey,
>
> It seems your problem was already reported in
> https://gitlab.isc.org/isc-projects/stork/-/issues/616 and
> https://gitlab.isc.org/isc-projects/stork/-/issues/818 . The bug fix
> was released in Stork 1.7.
>
> How long ago did you configure the Stork to monitor your HA pairs? Is
> it possible that it happened before 1.7?
The first stork version I installed was 1.12. It's been a while ago, but
I'm pretty sure that there weren't any changes in HA configuration.
> If you configured your Stork server in or after 1.7, did you perform
> some experiments with the HA configurations (e.g., changing HA type,
> swapping the primary and secondary servers, etc.) after registering
> their machines in Stork?
The pair of Kea servers that shows the problem has been in operation
before Stork was deployed and no changes in HA were made.
> I'm waiting for your feedback. I've opened
> https://gitlab.isc.org/isc-projects/stork/-/issues/1320 to analyze if
> the problem was fixed properly in 1.7 and should occur in new
> installations.
>
> Currently, the available solution for your problem is:
>
> 1. Unauthorize all Kea machines (there is the "Unauthorize" button in
> the hamburger menu on the /machines page)
> 2. Restart Stork agents
> 3. Authorize them again
>
> There is no need to touch any Kea components (Kea Control Agent or Kea
> DHCP daemons).
Please let me know if you need me to do additional troubleshooting
before unauthorizing agents.
Kind regards,
Andrey
More information about the Stork-users
mailing list