You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracked back to k3s-io/k3s#9184. This has changes the order of when the AgentReady channel is closed. This results in a endless loop, as kubelet waits for etcd to start, and etcd waits for the channel to be closed.
Steps To Reproduce:
Configure a cluster with at least 3 etcd-only nodes using Any of the Feburary 2024 RCs
Expected behavior:
All cluster nodes come up.
Actual behavior:
The 1st etcd nodes comes up partially, and the other 2 etcd nodes are stuck in an endless initialization loop.
Additional context / logs:
The text was updated successfully, but these errors were encountered:
RKE2 tracking for k3s-io/k3s#9540
Cluster Configuration:
3 Etcd only nodes
2 Control Plane nodes
1 Agent
Describe the bug:
Tracked back to k3s-io/k3s#9184. This has changes the order of when the
AgentReady
channel is closed. This results in a endless loop, as kubelet waits for etcd to start, and etcd waits for the channel to be closed.Steps To Reproduce:
Expected behavior:
All cluster nodes come up.
Actual behavior:
The 1st etcd nodes comes up partially, and the other 2 etcd nodes are stuck in an endless initialization loop.
Additional context / logs:
The text was updated successfully, but these errors were encountered: