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

[BUG] pool-coordinator isn't rescheduled when its node disconnects from others #1212

Closed
AndyEWang opened this issue Feb 9, 2023 · 3 comments · Fixed by #1218
Closed

[BUG] pool-coordinator isn't rescheduled when its node disconnects from others #1212

AndyEWang opened this issue Feb 9, 2023 · 3 comments · Fixed by #1218
Labels
kind/bug kind/bug

Comments

@AndyEWang
Copy link
Contributor

What happened:
when the node disconnects from all nodes except itself, pool-coordinator in this node cannot be evicted.

What you expected to happen:
pool-coordinator should be rescheduled into a healthy node.

How to reproduce it (as minimally and precisely as possible):
just shutdown the node where pool-coordinator is located and the Pod of pool-coordinator won't be rescheduled.

Anything else we need to know?:
found that charts/openyurt/templates/pool-coordinator.yaml is configured with

            tolerations:
              - effect: NoExecute
                operator: Exists

Environment:

  • OpenYurt version: 1.2
  • Kubernetes version (use kubectl version): 1.22

/kind bug

@AndyEWang AndyEWang added the kind/bug kind/bug label Feb 9, 2023
@rambohe-ch
Copy link
Member

@LaurenceLiZhixin @Congrool PTAL

@Congrool
Copy link
Member

Congrool commented Feb 9, 2023

I think we can remove such toleration from pool-coordinator. Would you like to submit a pr? @AndyEWang

@AndyEWang
Copy link
Contributor Author

@Congrool Ok, I will submit one if there is no special case to bind pool-coordinator to a node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug kind/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants