[stork-users] Removing a node and re-adding it back causes a certificate error

[Darren Ankney]

Hi Marek,

Have you tried removing the machine from the Stork GUI and then
re-registering as described here:
https://kb.isc.org/docs/stork-quickstart-guide#register-stork-agent or
here: https://kb.isc.org/docs/stork-quickstart-guide#register-stork-agent1
? It may work.

Thank you,
Darren Ankney

On Mon, May 6, 2024 at 6:05 PM <mxhajduczenia at gmail.com> wrote:

> Dear Forum,
>
>
>
> I had two nodes added to Stork: .130 and .131 and they were working
> correctly. Node .130 had a kernel failure due to changes I was trying to
> apply and I did not make a copy, unfortunately. Long story short, I had to
> re-install node .130, and then I wanted to add it back to Stork
>
>
>
>
>
> No matter what I do, I am getting the error shown above, i.e., Cannot get
> state of machine.
>
>
>
> Syslog review shows only one error message following two warning messages.
>
>
>
> May  6 21:58:38 server-kea-control stork-server[719]: time="2024-05-06
> 21:58:38" level="warning" msg="rpc error: code = Unavailable desc =
> connection error: desc = \"error reading server preface: remote error: tls:
> bad certificate\"" file="          manager.go:124  " agent="
> 172.17.129.130:8080"
>
> May  6 21:58:38 server-kea-control stork-server[719]: time="2024-05-06
> 21:58:38" level="warning" msg="Failed to get state from the Stork agent;
> the agent is still not responding" file="           grpcli.go:326  " agent="
> 172.17.129.130:8080"
>
> May  6 21:58:38 server-kea-control stork-server[719]: time="2024-05-06
> 21:58:38" level="warning" msg="failed to get state from agent
> 172.17.129.130:8080: grpc manager is unable to re-establish connection
> with the agent 172.17.129.130:8080: rpc error: code = Unavailable desc =
> connection error: desc = \"error reading server preface: remote error: tls:
> bad certificate\"" file="      statepuller.go:247  "
>
>
>
> I suspect that the TLS certificate does to get cleared when the machine is
> removed and a machine with the same IP address is re-added.
>
>
>
> I did not find a remedy for it for now and I do not fancy a complete
> re-install of Stork if I can avoid it.
>
>
>
> Any suggestions on how to fix it?
>
>
>
> Regards
>
>
>
> Marek
> --
> Stork-users mailing list
> Stork-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/stork-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20240507/ee0abc08/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 46237 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/stork-users/attachments/20240507/ee0abc08/attachment-0001.png>