Bug 1975379
| Summary: | Console pods are scheduled on single master node | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Apurva Nisal <anisal> |
| Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
| Status: | CLOSED ERRATA | QA Contact: | Yanping Zhang <yanpzhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | aos-bugs, eparis, gagore, jhadvig, jokerman, mmohan, ronald.rademaker, spadgett, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Use of soft requirement for anti-affinity rules on both console's deployments.
Consequence: Console pods are scheduled on single master node.
Fix: Use hard requirement for anti-affinity rules on both console's deployments. Use the hostname as topology key when scheduling the pods.
Result: Console pods are scheduled on different master node.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-18 17:36:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2003639 | ||
|
Description
Apurva Nisal
2021-06-23 14:34:25 UTC
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 |