-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
k3s-server creates improper etcd member name #9521
Milestone
Comments
This was referenced Mar 1, 2024
Reproduced issue on rke2 v1.26.14+rke2r1 and rancher v2.7.11
Issue is not reproducible in k3s
Validated there is no regression in k3s using latest rc on supported versions
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
K3s tracking issue for:
Appears to be a race condition caused by running
etcd-snapshot
commands while the server is initially starting up. If there are no etcd files, the snapshot command would bail out immediately, but if some of the files exist, the command would create the etcd/name file with an empty hostname, before the server can get around to doing it with the hostname set.This does not appear to have any serious negative impact on the cluster, other than the status condition not being set properly due to it failing to find any members whose name contains the node name. This could also be handled better, since the etcd member name is available in annotation and we don't need to rely on hostname matching.
The text was updated successfully, but these errors were encountered: