Closed cloudcafetech closed 1 day ago
Figure out why the etcd pod isn't running on the existing server node. Have you checked the kubelet.log, and etcd pod logs under /var/log/pods?
Note, RKE2 does not have "master" nodes. Just server and agents.
Looks like bug/issue was in v1.30.4, after changing new version (v1.30.5) issue fixed.
By the way, do you have any idea how to find right stable (bug/issue free) version ?
I'm not aware of any issues with etcd in v1.30.4+rke2r1, so it is unlikely that whatever was going on was resolved by the change in version. Without logs I really can't say though.
In general I'd recommend the latest version available. If we're aware of a bug, we either fix it, or call it out in the release notes.
Thank you for reply.
Based on your issue (https://github.com/rancher/rke2/issues/5804), I decided to check another version & it works.
Biggest challenge is is we setting up in Airgap Env :)
Once again thanks for prompt reply.
Environmental Info:
Node(s) CPU architecture, OS, and Version: Linux 5.14.0-427.33.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Aug 16 10:56:24 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: MASTER1:
MASTER2:
Able to reach Master on 9345
Describe the bug:
Not able to join master, error coming as below