loadbalancer not getting created

[TimHeckel]

hmmm, when I start from scratch with this config, the loadbalancer is not getting created. Interestingly, I can see some of the hetzner servers not getting powered up as the script is running, so I've been manually turning them on. That could of course be the problem! I will keep tearing down and trying again.

location                  = "ash" # change to `ash` for us-east Ashburn, Virginia location
network_region            = "us-east" # change to `us-east` if location is ash
agent_server_type         = "ccx22"
control_plane_server_type = "cpx11"
lb_server_type            = "lb11"

# At least 3 server nodes is recommended for HA, otherwise you need to turn off automatic upgrade (see ReadMe).
servers_num               = 3

# For agent nodes, at least 2 is recommended for HA, but you can keep automatic upgrades.
agents_num                = 3

Additionally, I do see this error in the logs - not sure if it's a problem?

module.agents[0].hcloud_server.server (remote-exec): Get:13 http://mirror.hetzner.com/debian/security bullseye-security/main amd64 Packages [120 kB]

module.control_planes[0].hcloud_server.server (remote-exec): 02/22 03:20:22 [ERROR] CUID#9 - Download aborted. URI=https://provo-mirror.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64-16.0.0-kvm-and-xen-Snapshot20220219.qcow2
module.control_planes[0].hcloud_server.server (remote-exec): Exception: [AbstractCommand.cc:351] errorCode=3 URI=https://provo-mirror.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64-16.0.0-kvm-and-xen-Snapshot20220219.qcow2
module.control_planes[0].hcloud_server.server (remote-exec):   -> [HttpSkipResponseCommand.cc:218] errorCode=3 Resource not found

[mysticaltech]

Check this issue, Hetzner sometimes fails to enter rescue and turns the server off. See #49

[TimHeckel]

Thanks for that - yeah I did that and perhaps it helped, but unfortunately the load balancer is not getting created. It's dying with the below failure:

null_resource.first_control_plane (remote-exec): Job for k3s.service failed because the control process exited with error code.
null_resource.first_control_plane (remote-exec): See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.
null_resource.first_control_plane (remote-exec): Waiting for the k3s server to start...
╷
│ Error: remote-exec provisioner error
│
│   with null_resource.first_control_plane,
│   on master.tf line 64, in resource "null_resource" "first_control_plane":
│   64:   provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_1261623817.sh": Process exited with status 124

Seems like the null in the null_resource.first_control_plane is problematic?

I am going to tear down and try again...

[mysticaltech]

There are no secrets that are supposed to be involved in the process. It's really weird.

[mysticaltech]

Ah I understand.

[mysticaltech]

You have to delete the cluster completely Tim!

[mysticaltech]

terraform destroy

And in another terminal

hcloud load-balancer delete k3s
hcloud network delete k3s

[mysticaltech]

Before starting, make sure that

hcloud server list

Returns nothing!

[TimHeckel]

Hey - just to close the loop, I pulled the latest from master and retried, and everything worked - I think the issue was a strange combination of things, likely something up with hetzner's api last night. Thanks!

[mysticaltech]

Great to hear @TimHeckel! 🚀