-
Notifications
You must be signed in to change notification settings - Fork 590
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
RKE cluster is stuck in "Removing member from etcd cluster" when removing/adding a node #3354
Comments
#3073 describes similar issue but it was closed without explanation and/or resolution. Sometime (1 out of 10 tries), the 1st node got replaced okay but the 2nd one got stuck Removing member [etcd-x.x.x.x] from etcd cluster forever. I've also tried rke up --config cluster.yaml withou update-only and it still can't remove the node from the etcd. For now, I have to do this workaround:
|
.30 is the NEW node but there is no hyperkube containers deployed. .61 is the OLD node and can't be removed from the etcd cluster because .30 can't join or what?
|
How did you restore from etcd? |
Hi! |
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions. |
RKE version: 1.3.15
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) AWS
cluster.yml file:
Steps to Reproduce: See rancher/rancher#42684
We need to rolling patch the Local cluster with a new AMI. This is what I did:
Results: See rancher/rancher#42684
It was able to remove the OLD node (.197)
.156 is the NEW node. RKE up doesn't install the hyperkube containers
The text was updated successfully, but these errors were encountered: