Skip to content
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

[Release-1.27] - Stopping service on ControlPlane node causes other nodes to go NotReady #9914

Closed
brandond opened this issue Apr 10, 2024 · 1 comment
Assignees
Milestone

Comments

@brandond
Copy link
Member

Backport fix for Stopping service on ControlPlane node causes other nodes to go NotReady

@fmoral2
Copy link
Contributor

fmoral2 commented Apr 15, 2024

Validated on Version:

-$ k3s version v1.27.12+k3s-2d48b196 (2d48b196)

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
SUSE Linux Enterprise Server 15 SP4

Cluster Configuration:
Split roles:

  • 2 cp only
  • 2 etcd
  • 1 worker

Steps to validate the fix

  1. create split roles cluster
  2. Stop server on one of the cp only
  3. check other nodes
  4. validate no other node is not ready or inactive
  5. validate pods

Reproduction Issue:

 
 

Validation Results:

       
       
- `Tried from 2 diff control plane nodes. It only stops the requested one.`

CP -2 
$ kubectl get nodes
NAME                                          STATUS     ROLES                       AGE   VERSION
ip-172-31-0-80.us-east-2.compute.internal     Ready      etcd                        14m   v1.27.12+k3s-2d48b196
ip-172-31-1-21.us-east-2.compute.internal     Ready      control-plane,master        14m   v1.27.12+k3s-2d48b196
ip-172-31-12-104.us-east-2.compute.internal   Ready      <none>                      12m   v1.27.12+k3s-2d48b196
ip-172-31-14-103.us-east-2.compute.internal   Ready      <none>                      12m   v1.27.12+k3s-2d48b196
ip-172-31-15-103.us-east-2.compute.internal   NotReady   control-plane,master        14m   v1.27.12+k3s-2d48b196
ip-172-31-4-156.us-east-2.compute.internal    Ready      <none>                      11m   v1.27.12+k3s-2d48b196
ip-172-31-5-224.us-east-2.compute.internal    Ready      etcd                        14m   v1.27.12+k3s-2d48b196
ip-172-31-7-127.us-east-2.compute.internal    Ready      control-plane,etcd,master   17m   v1.27.12+k3s-2d48b196


CP -1 
$ kubectl get nodes
NAME                                          STATUS     ROLES                       AGE   VERSION
ip-172-31-0-80.us-east-2.compute.internal     Ready      etcd                        15m   v1.27.12+k3s-2d48b196
ip-172-31-1-21.us-east-2.compute.internal     NotReady   control-plane,master        15m   v1.27.12+k3s-2d48b196
ip-172-31-12-104.us-east-2.compute.internal   Ready      <none>                      13m   v1.27.12+k3s-2d48b196
ip-172-31-14-103.us-east-2.compute.internal   Ready      <none>                      13m   v1.27.12+k3s-2d48b196
ip-172-31-15-103.us-east-2.compute.internal   Ready      control-plane,master        15m   v1.27.12+k3s-2d48b196
ip-172-31-4-156.us-east-2.compute.internal    Ready      <none>                      12m   v1.27.12+k3s-2d48b196
ip-172-31-5-224.us-east-2.compute.internal    Ready      etcd                        15m   v1.27.12+k3s-2d48b196
ip-172-31-7-127.us-east-2.compute.internal    Ready      control-plane,etcd,master   18m   v1.27.12+k3s-2d48b196

@fmoral2 fmoral2 closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants