Description of problem: Console pods are scheduled on single 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 Actual results: Console pods are scheduled on single master node Expected results: Console pods should be scheduled on different master node
We have anti-affinity rules set, but we're using `preferredDuringSchedulingIgnoredDuringExecution` which is the soft requirement rather than `requiredDuringSchedulingIgnoredDuringExecution` which is the hard requirement.
Still valid. PR up and in merge process.
Please backport the PR to release 4.7 as well Thx, Ronald
Reopening as this breaks OpenStack deployments.
Checked on ocp 4.9 cluster with payload 4.9.0-0.nightly-2021-07-19-140945。 Check console/downloads deployment yaml, the anti-affinity rule is "requiredDuringSchedulingIgnoredDuringExecution". And console pods are scheduled on different master nodes. # oc get node |grep master ip-10-0-158-130.us-east-2.compute.internal Ready master 9h v1.21.1+8268f88 ip-10-0-160-245.us-east-2.compute.internal Ready master 9h v1.21.1+8268f88 ip-10-0-196-96.us-east-2.compute.internal Ready master 9h v1.21.1+8268f88 # oc get pod -n openshift-console -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES console-66946dc647-2vp26 1/1 Running 0 9h 10.128.0.36 ip-10-0-158-130.us-east-2.compute.internal <none> <none> console-66946dc647-wpg64 1/1 Running 0 9h 10.130.0.35 ip-10-0-160-245.us-east-2.compute.internal <none> <none> downloads-7d9df5cb76-5fsmr 1/1 Running 0 9h 10.130.0.28 ip-10-0-160-245.us-east-2.compute.internal <none> <none> downloads-7d9df5cb76-x44nc 1/1 Running 0 9h 10.128.0.23 ip-10-0-158-130.us-east-2.compute.internal <none> <none>
Hi Guys, Can it be backported to release 4.7 as well ? Thx, Ronald
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security 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. https://access.redhat.com/errata/RHSA-2021:3759
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days