mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-17 20:00:07 +00:00
2b18086a25
The assume cache logs adding assumed claims at V(4) but there wasn't anything about in-flight claims in the log for a scheduling failure where the same device was allocated twice (https://github.com/kubernetes/kubernetes/issues/133602). Debugging that issue depends on seeing all changes related to assume cache changes (not just the single "Assumed object") and in-flight claims. We could make them all V(4) (= "debug level") but they seem more appropriate for V(5) (= "trace level"), so the assume cache verbosity gets toned down to that.