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] ApplyForAll devices but failed #1869

Closed
eahydra opened this issue Jan 25, 2024 · 0 comments · Fixed by #1870
Closed

[BUG] ApplyForAll devices but failed #1869

eahydra opened this issue Jan 25, 2024 · 0 comments · Fixed by #1870
Labels
area/koord-scheduler kind/bug Create a report to help us improve

Comments

@eahydra
Copy link
Member

eahydra commented Jan 25, 2024

What happened:

There are 4 RDMA devices with label "type=fakeW" and 1 RDMA device with "type=fakeS" on the node named "node-1".
and create a Pod with the device allocation hint as following request "koordinator.sh/rdma=1"

{
    "rdma": {
        "selector": {
            "matchLabels": {
                "type": "fakeW"
            }
        },
        "allocateStrategy": "ApplyForAll"
    }
}

What you expected to happen:

Expected the Pod can be schedule on node-1, but failed with message Insufficient rdma devices

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

Anything else we need to know?:

Environment:

  • App version: koordinator v1.4.0
  • Kubernetes version (use kubectl version): 1.22
  • 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