Bug 1909587
| Summary: | [OCP4] all of the OCP master nodes with soft-anti-affinity run on the same OSP node | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Hideshi Fukumoto <hfukumot> |
| Component: | Installer | Assignee: | Pierre Prinetti <pprinett> |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | weiwei jiang <wjiang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | crawford, m.andre, mbooth, pprinett, wjiang |
| Version: | 4.6.z | Keywords: | UpcomingSprint |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:47:16 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: | 1916297 | ||
|
Comment 5
weiwei jiang
2021-01-11 09:18:05 UTC
The 4.6.z backport is currenly awaiting approval from the Release manager. No further action is expected on your (or our) side at this time. Thank you! Bug 1916297 Checked with more than 3 master again with 4.7.0-0.nightly-2021-01-22-063949, and it works well. ./openshift-install 4.7.0-0.nightly-2021-01-22-063949 built from commit f0f10f6086f2e0446362ed7378b13ba6ed88e7e1 release image registry.ci.openshift.org/ocp/release@sha256:7e62d6eced986e77be37153e8e38069163e0457e29859664ff6d016dbdca0b3b # openstack server group show wj47ios122aw-tzsnx-master +----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | id | 3db57d3f-7517-48f6-b26a-ace8430b94b5 | | members | 3ba2c989-76a9-47ff-bda6-080dd8941e61, ba0f3775-f416-48c9-ba5c-f46051742d71, dc267f08-8567-4777-89e4-6f30d79f924f, ebc042a1-0228-4f2d-bc79-36a1450edab1, f4650415-ff24-497d-b682-7961fbf27358 | | name | wj47ios122aw-tzsnx-master | | policies | soft-anti-affinity | +----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ # for i in `openstack server list --name wj4 -f value -c Name |grep -i master`; do openstack server show $i ; done |grep -i hostid | hostId | 6a2ee645e9f14b9f0e702891f333307b2f5a18562fc3ea7e7f52607e | | hostId | 2bdc41f55878483467141fba5dec5dd18a5b6e5935c29d536cce6296 | | hostId | b2819cfacdc3cc8ea3735a801f5c44ae30b20eae3009e4fd8e2e9917 | | hostId | 90d74f34572f5cf1523a3b6490e03fe63e05e03b44cdfe2b7d00a964 | | hostId | b71246d7dab294fde8273ee4322f60abf5c7f8978726e2892d008a97 | How about from OpenShift's perspective, do you see five control plane nodes in your cluster? Scratch that. I misread the previous command you were running and now I'm very confused. The fix for this issue hard codes the number of control nodes at three. How is it that you ended up with five nodes? What created the other two? (In reply to Alex Crawford from comment #10) > Scratch that. I misread the previous command you were running and now I'm > very confused. The fix for this issue hard codes the number of control nodes > at three. How is it that you ended up with five nodes? What created the > other two? The patch indeed changed the terraform code to always provision 3 control plane instances. However, we're still creating 'n' machine objects, where 'n' is the number of replicas specified in the control plane machine pool. Wouldn't then MAO notice these objects once the control plane is up and provisions the missing instances? The control plane isn't represented by MachineSets and Machines though. Only the workers make use of that right now. It's been on our backlog for a long time, but we haven't gotten around to managing the control nodes the same way that we manage the compute nodes. Maybe my understanding is dated. I had some time to dig into this further and was able to reproduce the behavior described, but on AWS. My understanding was dated. Sorry for the noise. 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.7.0 security, bug fix, and enhancement 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-2020:5633 |