Open quinncomendant opened 1 year ago
Does anyone ever experience a problem, research it for an hour, find the cause, then go to GitHub to report the issue but then discover that you already created a ticket five months earlier for exactly that issue with exactly the same solution?
Because I just did that. 🤦♂️
Describe the bug
Algo fails on Hetzner’s USA locations when using the
cx11
server size, which is the default included in Algo’sconfig.cfg
file. The Hetzner Cloud API responds with:This is not necessarily a bug in Algo, since the same error occurs when trying to create a
cx11
server using Hetzner's CLI tools.I asked Hetzner why this error occurs, and they replied:
So, the fix is to update Algo's
config.cfg
file to use servercpx11
instead ofcx11
(cpx11
is the smallest server size that is available in all Hetzner locations; it has 2 vCPUs instead of 1, and costs €3.85 instead of €3.29 per month):To Reproduce
Steps to reproduce the behavior:
./algo
Hetzner Cloud
.ash
orhil
.fatal: [localhost]: FAILED! => {"changed": false, "msg": "error during placement"}
.Expected behavior
Algo's default config should work for all providers and all locations.
Additional context
Here's the full
ANSIBLE_VERBOSITY=4
error output to help people find this ticket: