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] failed case: enable Node FullPCPUsOnly and request bind CPU with preferredCPUBindPolicy #1890

Closed
eahydra opened this issue Feb 4, 2024 · 0 comments · Fixed by #1891
Labels
area/koord-scheduler kind/bug Create a report to help us improve

Comments

@eahydra
Copy link
Member

eahydra commented Feb 4, 2024

What happened:

  1. Enable the node FullPCPUsOnly with label node.koordinator.sh/cpu-bind-policy=FullPCPUsOnly.
  2. Create Pod with scheduling.koordinator.sh/resource-spec and enable preferredCPUBindPolicy=FullPCPUsOnly.
  3. Failed to scheduling with the node.

What you expected to happen:

Pass the scheduling.

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

Anything else we need to know?:

Environment:

  • App version: koordinator 1.4.0
  • Kubernetes version (use kubectl version): 1.24
  • 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:
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
1 participant