JonasProgrammer / JonasProgrammer/docker-machine-driver-hetzner
Problem with Rancher when scaling up
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 438
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Version 5.0.2
Rancher: 2.8.0
Hello,
we have been using rancher in combination with the hetzner node driver for at least two years now and it worked entirely fine. However, all for sudden it seem we cannot scale up any nodes anymore.
During creation this the process stops throwing:
Flag provided but not defined: -hetzner-wait-on-error:Timeout waiting for ssh key.
I tried to add to the node template:
--hetzner-wait-on-error=40
--hetzner-wait-on-polling=40
to the Engine options with no effect. Likewise added it to the environment variable with no effect. I assume that the API is reuesting further parameters, which i cannot properly pass, but i have no idea at the moment where to start investigating.
What I can say is that the machines are not even created anymore at hetzner. This used to work perfectly well, but for some reasons does not work anymore. I also set up a new API token to ensure, that this is not the problem, but no effect.
Any ideas? Anyone had similar issues? This is having a dramatic impact on our cluster, since we cannot scale anymore at all while manually adding new nodes is not possible either...
Any sort of help appreciated!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing node creation with Rancher 2.8.0 and the Hetzner node driver using the reported engine options, then trace where the Flag provided but not defined and SSH-key timeout occur. Confirm whether scaling creates machines at Hetzner and whether the documented options are accepted; done means node creation and scaling work without those errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100