[stork-users] problems re-registering agent

[Slawek Figiel]

Hello Roland!

I'm glad to hear your original problem has been solved.

Could you provide some logs generated when you try registering the 
machine using the server token?

Regards,
Slawek Figiel

On 27/08/2024 12:02, DDFR | Ronald Blaas wrote:
> And just to be complete
> 
> I am registering with a server token.
> 
> 
> I have now tried registering the agent without a token which is working 
> just fine (after authorizing the agent in stork server)
> 
> Still wondering why the server token option is not working / ping not 
> working
> 
> Regards,
> 
> Ronald
> 
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of 
> DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> *Sent:* Tuesday, August 27, 2024 11:49
> *To:* Stork-users <stork-users at lists.isc.org>
> *Subject:* Re: [stork-users] problems re-registering agent
> So I am now a step further.
> 
> I had a mismatch in version number (server vs agent)
> Agent was upgrade to v1.18 whilst server was still on v1.15
> 
> After upgrading the server I see the token being installed on the client 
> but no I am facing an issue saying cannot ping machine.
> 
> I can ping the server from client as well as the client from server.
> So i am a bit confused what is going wrong here.
> 
> Any insights?
> 
> Regards,
> ROnald
> 
> 
> 
> ------------------------------------------------------------------------
> *From:* Stork-users <stork-users-bounces at lists.isc.org> on behalf of 
> DDFR | Ronald Blaas <ronald.blaas at ddfr.nl>
> *Sent:* Tuesday, August 27, 2024 10:47
> *To:* Stork-users <stork-users at lists.isc.org>
> *Subject:* [stork-users] problems re-registering agent
> Hi all,
> 
> Today I updated my ubuntu system and with the update kea (and stork 
> agent) have been updated.
> The result is that stork is able to see the status of kea load balancing 
> but is unable to communicate with the stork agent.
> 
> After some investigation it appears that there is a problem with the 
> certificate.
> 
> I am trying to re-register the agent but running into an error:
> 
> ERRO[2024-08-27 10:38:31]         register.go:368   Problem registering 
> machine                   error="missing serverCertFingerprint in 
> response from server for registration request"
> FATA[2024-08-27 10:38:31]             main.go:321   Registration failed
> 
> Any help how to fix this?
> 
> Kind regards,
> 
> Ronald
>