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] When koord-manager crashes, the koord-scheduler will fail to start if it is rebuilt. #1844

Closed
eahydra opened this issue Jan 16, 2024 · 1 comment · Fixed by #1845
Closed
Assignees
Labels
area/koord-scheduler kind/bug Create a report to help us improve

Comments

@eahydra
Copy link
Member

eahydra commented Jan 16, 2024

What happened:

  1. Set the koord-manager webhook configuration's failurePolicy to fail.
  2. Scale the koord-manager's replicas to 0.
  3. Delete the koord-scheduler pod.
  4. The koord-scheduler will fail to start.

What you expected to happen:

The newly created scheduler starts successfully.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • App version:
  • Kubernetes version (use kubectl version):
  • Install details (e.g. helm install args):
  • Node environment (for koordlet/runtime-proxy issue):
    • Containerd/Docker version:
    • OS version:
    • Kernal version:
    • Cgroup driver: cgroupfs/systemd
  • Others:
@eahydra eahydra added kind/bug Create a report to help us improve area/koord-scheduler labels Jan 16, 2024
@eahydra
Copy link
Member Author

eahydra commented Jan 16, 2024

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/koord-scheduler kind/bug Create a report to help us improve
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant