[stork-users] Stork Server and Agent versions

Darren Ankney darren.ankney at gmail.com
Fri Aug 25 10:35:27 UTC 2023


Hi,

I'm glad you were able to get it working.  I don't see any mention of
incompatible changes here:
https://gitlab.isc.org/isc-projects/stork/-/wikis/Releases/Release-notes-1.12.0
 A quick look over the ARM:
https://stork.readthedocs.io/en/v1.12.0/overview.html didn't seem to
show anything either. If it is indeed the case that the versions must
match, then hopefully that will become more clear in the future as you
suggest.

Thank you,

Darren Ankney

On Thu, Aug 24, 2023 at 3:19 PM Justin Krejci <JKrejci at usinternet.com> wrote:
>
> I had a Stork server running and talking to a Stork agent on a Kea server. Both machines are running Ubuntu. Everything was working fine. Then one day recently the Stork server and the Stork agent were not communicating properly. No config changes were made prior to this new problem but I did run a system update and reboot on the Stork server and I think the Stork server version was updated.
>
>
> Seeing this in the logs on the stork server
>
>
> stork-server[1661]: time="2023-08-24 13:42:53" level="warning" msg="rpc error: code = Unimplemented desc = grpc: Decompressor is not installed for grpc-encoding \"gzip\"" file="          manager.go:124  " agent="216.17.94.7:8081"
> stork-server[1661]: time="2023-08-24 13:42:53" level="warning" msg="failed to get state from agent 216.17.94.7:8081: grpc manager is unable to re-establish connection with the agent 216.17.94.7:8081: rpc error: code = Unimplemented desc = grpc: Decompressor is not installed for grpc-encoding \"gzip\"" file="      statepuller.go:247  "
>
> I tried removing and re-registering the Stork agent to the Stork server. That part works fine, but the Stork server web UI just immediately reports to "Cannot get state of machine" with the above log entries in syslog.
>
>
> Stork server version: 1.12.0.230802125039
>
> Stork agent version: 1.11.0.230606131857
>
>
> I updated the stork agent to version 1.12.0.230802125032 and now the stork server can properly query the agent again.
>
>
> Admittedly I did not read the Stork change logs or release notes, but will version differences not generally be tolerated or did I just catch an uncommon change that breaks compatibility between versions? Or is there something else I am missing? Perhaps the Stork server could identify version mismatches with its agents and flag them more visibly either in the web ui or in the log files.
>
>
> Anyways, thanks for this Stork software (while I am at it thanks also for Kea and dhcpd and bind too).
>
>
>
> --
> Stork-users mailing list
> Stork-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/stork-users


More information about the Stork-users mailing list