# How do you guys debug FailedScheduling?

**URL:** <https://discuss.kubernetes.io/t/how-do-you-guys-debug-failedscheduling/31594>\
**Category:** General Discussions\
**Created:** [February 13, 2025, 8:37pm UTC](https://discuss.kubernetes.io/t/how-do-you-guys-debug-failedscheduling/31594 "2025-02-13T20:37:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rooty0](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/rooty0/32/16929_2.png) [@rooty0](https://discuss.kubernetes.io/u/rooty0)\
**Post date:** [February 13, 2025, 8:37pm UTC](https://discuss.kubernetes.io/t/how-do-you-guys-debug-failedscheduling/31594/1 "2025-02-13T20:37:16Z")

</div>

Hey everyone,  
I have a pod stuck in a `FailedScheduling` pending state. I’m trying to schedule it to a specific node that I know is free and unused, but it just won’t go through.

Now, this is happens because of this:

```auto
Warning FailedScheduling 2m14s (x66 over 14m) default-scheduler 0/176 nodes are available: 10 node(s) had untolerated taint {wg: a}, 14 Insufficient cpu, 14 Insufficient memory, 14 Insufficient nvidia.com/gpu, 2 node(s) had untolerated taint {clustertag: a}, 3 node(s) had untolerated taint {wg: istio-autoscale-pool}, 34 node(s) didn't match Pod's node affinity/selector, 42 node(s) had untolerated taint {clustertag: b}, 47 node(s) had untolerated taint {wg: a-pool}, 5 node(s) had untolerated taint {wg: b-pool}, 6 node(s) had untolerated taint {wg: istio-pool}, 6 node(s) had volume node affinity conflict, 7 node(s) had untolerated taint {wg: c-pool}. preemption: 0/176 nodes are available: 14 No preemption victims found for incoming pod, 162 Preemption is not helpful for scheduling.

```

It’s a bit hard to read since there’s a lot going on – tons of taints, affinities, etc. Plus, it’s not even showing which exact nodes are causing the issue. For example, it just says something vague like _“47 node(s) had untolerated taint,”_ without mentioning specific node names.

Is there any way or tool where I can take this pending pod and point it at a specific node to see the exact reason why it’s not scheduling on that node? Would appreciate any help

Thanks!
