-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Creation on new cluster stuck on configuring agent node #1289
Comments
Now when running again I see the following logs for
|
This terraform thing is too flakey i'm afraid. As far as I'm concerned, it has worked for a few days. Now I cannot create nodeools anymore. It's stuck in creating state even though the servers are up and running in the Hetzner console. |
Might be connected to the (unresolved) discussion I started recently #1287 I'm having weird behaviour after updating the nodes with a recent microos update. Weird network connectivity issues, that I couldn't figure out yet (I just rolled back and disabled updates for now). Edit: I also saw some "503 Service Unavailable" and "connection refused" in my logs. I know those are very generic errors, but still. |
@kube-hetzner/core Any ideas? @mateuszlewko Try with |
Hi, I got the same error |
Hmm, I might have had the same too, I had nodes unable to come back to life after a reboot after a k3s upgrade. Replaced the nodes (long live longhorn) and turned off upgrades. Have not verified that this was the real problem though, but haven't seen it happen again either. No need to roll back anything though: the fresh nodes are on the latest k3s and have microos updating weekly without issues. Just not automatically upgrading k3s. |
Considering this as a occasional hiccup, but will monitor the situation. |
@kimdre Could you share your kube.tf please. |
@mateuszlewko Did you manage to make it work? What about you @andi0b ? |
I disabled wireguard and recreated the cluster some time later. I haven't checked if wireguard works better with cillium or if that was the actual problem. |
No, I'm currently on easter holiday and didn't investigate it more. I just disabled kured (I think with something like |
Folks, this was probably due to a bug in system upgrade controller, now fixed. Make sure to upgrade with |
Description
I'm launching a new cluster on the latest version of this package. I'm using ed25519 ssh keys without a password. Creation of completely new cluster seems to be stuck (for > 40 min) on configuration of a single agent node (the server is present in hetzner UI).
This is the last excerpt from logs:
Kube.tf file
Screenshots
No response
Platform
Mac
The text was updated successfully, but these errors were encountered: