+++ This bug was initially created as a clone of Bug #1820343 +++ Currently, setting `LogLevel` in the kube-scheduler to `TraceAll` only sets the kube-scheduler's loglevel (--v flag) to 8 (see [1]). Since many of the scheduler's logs are at level 10 (such as scoring[2]), it would be much more helpful if the operator could configure 10 for TraceAll instead of 8 [1] https://github.com/openshift/cluster-kube-scheduler-operator/blob/01caed9c867a7f8fa87ac15b3bdf9335d98ef21e/pkg/operator/target_config_reconciler_v410_00.go#L144 [2] https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/core/generic_scheduler.go#L650-L654
For QA, to verify this you should set the scheduler config (oc edit schedulers/cluster) to include the line `logLevel: TraceAll` in the spec. Then, once the kube-scheduler pods have restarted, they should have a flag `-v=10` in the kube-scheduler container
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409