Bug is the clone of https://bugzilla.redhat.com/show_bug.cgi?id=1975379 to backport the fix to 4.7
Console pods are scheduled on same master node.
oc get pods -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
console-6558bcb9f9-7cnjk 1/1 Running 1 3d1h 10.129.0.38 master-1.abc.com <none> <none>
console-6558bcb9f9-fwpzf 1/1 Running 0 3d1h 10.129.0.46 master-1.abc.com <none> <none>
downloads-84f554976-9nwr2 1/1 Running 0 3d1h 10.131.0.11 worker-2.abc.com <none> <none>
downloads-84f554976-wl655 1/1 Running 0 3d1h 10.129.2.7 worker-0.abc.com <none> <none>
oc get nodes
NAME STATUS ROLES AGE VERSION
master-0.abc.com Ready master 3d1h v1.20.0+df9c838
master-1.abc.com Ready master 3d1h v1.20.0+df9c838
master-2.abc.com Ready master 3d1h v1.20.0+df9c838
worker-0.abc.com Ready worker 3d1h v1.20.0+df9c838
worker-1.abc.com Ready worker 3d1h v1.20.0+df9c838
worker-2.abc.com Ready worker 3d1h v1.20.0+df9c838
Console Pod is getting scheduled on same master node due to `preferredDuringSchedulingIgnoredDuringExecution` which is the soft requirement rather than `requiredDuringSchedulingIgnoredDuringExecution` which is the hard requirement.
Console pods are scheduled on the same master node
Console pods should be scheduled on the different master node
Just for note: this should be tested on a regular cluster, not a single node cluster, since that feature was introduced in 4.8
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 (OpenShift Container Platform 4.7.37 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.