[stork-users] Stork does not report Kea version upgrade from 2.2.1 to 2.4.0

Slawek Figiel slawek at isc.org
Fri Oct 6 17:20:48 UTC 2023


Hello Kevin!

I'm trying to repeat your problem.

Could you check for me some data in your Stork server?

1. Check if the machine list (/machines/all) not display your machine on 
the "Unauthorized" list.
2. Open the machine page (e.g., /machines/1) related to the problematic 
Kea daemon. There is "Applications" column in the middle. Check if the 
version showed there is correct.
3. Go to the application page related to the problematic Kea daemon 
(e.g., /apps/kea/1). Click the "DHCPv4" or "DHCPv6" (depending on the 
type of your Kea daemon) tab, Is the version showed there correct?
4. Click on the "CA" tab. Is the version showed there correct?

 > Is there something else I should do to get Stork to recognize/report 
the version change?

No, it isn't; the version is updated without additional interaction. It 
isn't updated immediately because first, the Stork agent needs to detect 
the changes in the daemon process, and then, the Stork server needs to 
pull the data from the agent. But it should take at most 2 minutes.

The version may not be updated if the Stork agent has no access to the 
Kea process details or if there is a connectivity problem.

Regards,
Slawek


On 01/10/2023 13:28, Kevin P. Fleming wrote:
> A few days ago I upgraded my Kea servers from 2.2.1 to 2.4.0, and also 
> changed their HA configuration from load-balancing to hot-standby.
> 
> The Stork dashboard correctly shows the HA configuration change, but 
> does not show the version change. I've restarted the agent on one of the 
> servers but that has not resolved the issue.
> 
> Is there something else I should do to get Stork to recognize/report the 
> version change?
> 


More information about the Stork-users mailing list