JonasProgrammer / JonasProgrammer/docker-machine-driver-hetzner
Rancher - VMs are not removed from Hetzner, when got storage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 438
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Hi Jonas
I've been using the hetzner driver for a many months, going through a numerous version.
I'm using the driver in Rancher, a few days ago I updated the driver from v3.11.x to 5.0.1 .
Scaling down doesn't remove the virtual machine itself.
Maybe it's because these my servers have storage devices attached, which must be detached first.
Rancher v2.7.9 (upgraded several times)
Node driver is configured as folowing:
Download URL: https://github.com/JonasProgrammer/docker-machine-driver-hetzner/releases/download/5.0.1/docker-machine-driver-hetzner_5.0.1_linux_amd64.tar.gz
UI: https://storage.googleapis.com/hcloud-rancher-v2-ui-driver/component.js
whitelist domains: storage.googleapis.com
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 Rancher scale-down with a Hetzner VM that has attached storage, comparing it with a VM without storage. Trace the driver’s scale-down behavior and verify that the VM and its attached storage are cleaned up as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100