Mock devices never report healthy — Allocatable never shows registered GPU resources #21

Activity

1. coderabbitai commented on Jul 29, 2026

   

   coderabbitaiBot

   on Jul 29, 2026 – with coderabbitai

   More actions

   ⚠️ Possible Duplicate Issue(s)

   • Unable to see GPU allocation using mock-device-plugin on Kind cluster (Mac) #16

   🔗 Related PRs

   #18 - feat(ascend,hygon): register AI-core/dcucores and support new and legacy vnpus config [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
2. hollarhollar commented on Jul 29, 2026

   

   hollarhollar

   on Jul 29, 2026

   Author

   More actions

   Update: this does look like the same issue as #16 (same Kind + no-real-GPU environment, same symptom). I tried the MOCK_DEVICE_FORCE_REGISTER=true env var patch mentioned there:

   kubectl patch daemonset hami-mock-device-plugin-daemonset -n kube-system
   --type='json' -p='[{"op":"add","path":"/spec/template/spec/containers/0/env/-","value":{"name":"MOCK_DEVICE_FORCE_REGISTER","value":"true"}}]'

   Confirmed the env var landed in the running pod, but it made no difference — the "unhealthy" cycling continues identically for every device type. So that specific workaround doesn't appear to resolve it, at least not on Kind.

   Combined with @DSFans2014's explanation on #14 (that this log fires when a device is configured but has no corresponding node.status.capacity resource, and that the real device plugin + matching hardware is required) — it seems like mock-device-plugin may not currently work standalone on GPU-less environments like Kind, despite the README's framing suggesting it should. Happy to help narrow this down further if there's a specific config or setup step I'm missing, or to help document the actual constraint once it's clear.

   Investigated with Claude Code assistance; reproduction steps and findings are my own testing.
3. DSFans2014 commented on Jul 30, 2026

   

   DSFans2014

   on Jul 30, 2026

   Member

   More actions

   mock-device-plugin simply parses the annotation and then register the resources. If you want to simulate GPUs on a machine without GPU devices, please use other components such as fake-gpu.
4. hollarhollar commented on Jul 30, 2026

   

   hollarhollar

   on Jul 30, 2026

   Author

   More actions

   Thanks @DSFans2014, that clears it up. Makes sense, I'll follow up with a small PR to the README clarifying that mock-device-plugin requires an existing GPU-annotated node rather than working standalone on hardware-free environments, and pointing to fake-gpu for that use case instead. Appreciate the quick response!
5. moezdil commented on Sep 22, 2026

   

   moezdil

   on Sep 22, 2026

   More actions

   Old PRs and issues are being closed because they are no longer relevant. Or it was closed because of th
   inactivity or PR/issues owners.
   If you believe the issue is still relevant, please submit feedback.
6. moezdil

   closed this as completedon Sep 22, 2026