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

Deleted Pending Pods count as active in Pod Groups #2208

Closed
alculquicondor opened this issue May 15, 2024 · 1 comment · Fixed by #2212
Closed

Deleted Pending Pods count as active in Pod Groups #2208

alculquicondor opened this issue May 15, 2024 · 1 comment · Fixed by #2212
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@alculquicondor
Copy link
Contributor

What happened:

A Pending Pod (a Pod that doesn't have a scheduling gate, but it never got scheduled) is still considered as an "active" pod that cannot yet be replaced.

return utilslices.Pick(p.list.Items, isPodRunnableOrSucceeded)

What you expected to happen:

A replacement Pod for a Pod that never got scheduled should be allowed to run

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

  1. Create a Pod, part of a pod group, with an unsatisfiable node-selector
  2. Wait for the group to be admitted.
  3. Delete the Pod manually
  4. Create a replacement Pod (this Pod should not be deleted)

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Kueue version (use git describe --tags --dirty --always):
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@alculquicondor alculquicondor added the kind/bug Categorizes issue or PR as related to a bug. label May 15, 2024
@alculquicondor
Copy link
Contributor Author

/assign @trasc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants