Replies: 2 comments
-
Hi, @ace-yong. Thanks for raising this issue. Have you referred to #15929 or #14514? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please reproduce this issue and provide the complete etcd log. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug report criteria
What happened?
I deployed a single-node etcd in a single-node k3s, and during normal operation, I used reboot to restart the host machine. After booting up, the etcd startup reported the following error:
The subsequent logs repeatedly print "failed to publish local member to cluster through raft". I have confirmed that the k3s DNS is functioning correctly, and the flannel network is also normal. I cleared the data in /bitnami/etcd/data within etcd, and after restarting etcd, it began to operate normally. The logs are as follows:
I would like to understand why etcd got stuck in a "failed to publish local member to cluster through raft" loop, and how deleting the data restored normal functionality.
What did you expect to happen?
etcd started normally and is providing services.
How can we reproduce it (as minimally and precisely as possible)?
It's unclear how to reproduce this issue, as in the past, I have also rebooted the host machine without encountering this problem.
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions