Bug 1849171
| Summary: | [OSP] Floating IP specified with lbFloatingIP in install-config.yaml fails to attach to master node causing install to fail | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> | |
| Component: | Installer | Assignee: | Martin André <m.andre> | |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | adhingra, akaris, asimonel, dsanzmor, eduen, fbrychta, mabajodu, m.andre, mfedosin, pprinett, rstarr, tsedovic, wjiang | |
| Version: | 4.2.0 | Keywords: | TestBlocker | |
| Target Milestone: | --- | |||
| Target Release: | 4.3.z | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: The Terraform step "openstack_networking_floatingip_associate_v2" did not list all its dependendent steps.
Consequence: The required step "openstack_networking_router_interface_v2.nodes_router_interface" was not always executed before the FIP association. This caused a race condition that occasionally failed the Terraform job, especially on overloaded systems.
Fix: List the dependant Terraform step as "depends_on" to force the router to be created before the FIP is attached to the port.
Result: The Terraform steps run in the correct order, ensuring that the FIP association does not result in a "Resource not found" error.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1850940 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-07 14:48:26 UTC | Type: | --- | |
| 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: | 1847957 | |||
| Bug Blocks: | 1850940 | |||
|
Comment 3
David Sanz
2020-06-25 09:58:27 UTC
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:2805 |