-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.12
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When using "oc describe pod" to check pod status, I see the following message: 4h17m Warning FailedScheduling pod/mypod-topo 0/5 nodes are available: 5 persistentvolumeclaim "mypvc-topo" not found. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling. 4h17m Warning FailedScheduling pod/mypod-topo running PreFilter plugin "VolumeBinding": %!!(MISSING)w(<nil>) The "%!!(MISSING)w(<nil>)" looks a bit strange and messy. This is the log from schedule pod: E0612 05:09:49.117551 1 schedule_one.go:131] "Error selecting node for pod" err="running PreFilter plugin \"VolumeBinding\": %!w(<nil>)" pod="wduan/mypod-topo" E0612 05:09:49.117780 1 schedule_one.go:842] "Error scheduling pod; retrying" err="running PreFilter plugin \"VolumeBinding\": %!w(<nil>)" pod="wduan/mypod-topo"
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2023-06-07-221552
How reproducible:
Once (The scheduler went back to work in 10~ mins later.)
Steps to Reproduce:
create pvc and pod in a vSphere cluster
Actual results:
Got log like FailedScheduling: running PreFilter plugin "VolumeBinding": %!!(MISSING)w(<nil>), looks like messy
Expected results:
The log should not be messy.
Additional info: