failed: failed to set ssh key: The key already exists (KEY_ALREADY_EXISTS)

[Stringls]

Hi! It seems like BM server wasn't deprovisioned completely or at all and when I try to setup the cluster again the BM host is always in the preparing state. CAPH controller gives the below error

action \"preparing\" failed: failed to set ssh key: The key already exists (KEY_ALREADY_EXISTS)","errorVerbose":"The key already exists (KEY_ALREADY_EXISTS)\nfailed to set ssh key

How to reset the ssh key or deprovision BM server so I can setup it again?

[janiskemper]

The problem is here probably that the key exists in Robot with another name. Same SSH key, but a different name. Can you please check that? This is an issue that we have experienced multiple times as well when we named the key wrongly and this happens...

[Stringls]

Yeah, I've changed the Hetzner project and using another key. The name if different, not sure about the key data

[janiskemper]

In HCloud, you don't necessarily have to specify a key - only if you want.
In Robot we need it to provision the server. As we have access to the full (public) key, we can also upload it with the controller in case the user didn't do it yet. That's what we do.
You can name the ssh key however you want!

I don't really understand the problem you have with creating a new one and specifying it in the specs. Can you elaborate?

[Stringls]

All good right now, I've managed out how it works, thanks.

In HCloud, you don't necessarily have to specify a key - only if you want.

In the docs it says that we have to specify HCloud SSH key name.

sshKeys.hcloud.name | string |   | yes | Name of SSH key

So I am not sure what you mean by it's not necessary

[janiskemper]

The name of the ssh key you specified in HCloud is required here!

[janiskemper]

But I'm very happy that you made it work!

[Stringls]

Thank you for help! I'll close the discussion as completed