Bug 1850940 - [OSP] Floating IP specified with lbFloatingIP in install-config.yaml fails to attach to master node causing install to fail
Summary: [OSP] Floating IP specified with lbFloatingIP in install-config.yaml fails to...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.2.0
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 4.2.z
Assignee: Eric Duen
QA Contact: David Sanz
Depends On: 1849171
TreeView+ depends on / blocked
Reported: 2020-06-25 08:39 UTC by Pierre Prinetti
Modified: 2020-07-27 19:23 UTC (History)
16 users (show)

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.
Clone Of: 1849171
Last Closed: 2020-07-27 19:23:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3804 0 None closed Bug 1850940: OpenStack: Wait for router to create FIP 2020-12-15 04:58:23 UTC

Description Pierre Prinetti 2020-06-25 08:39:58 UTC
+++ This bug was initially created as a clone of Bug #1849171 +++

+++ This bug was initially created as a clone of Bug #1847957 +++

+++ This bug was initially created as a clone of Bug #1846297 +++

+++ This bug was initially created as a clone of Bug #1734460 +++

Description of problem:

During the openshift on openstack install process a floating IP is being attached to the bootstrap node. It's failing to attach the floating IP specified in install-config.yml to the api node and another floating IP from the pool is attached to the bootstrap node.

Taken from openshift-install release-4.2 branch.

How reproducible: always

Steps to Reproduce:
1. Deploy OSP
2. Run openshift-install

Actual results:

DEBUG module.masters.openstack_compute_instance_v2.master_conf[0]: Creation complete after 54s [id=4d641422-0e3d-4db5-90b1-baf9f031f55e] 
ERROR Error: Error associating openstack_networking_floatingip_associate_v2 floating_ip e8b95280-334a-4988-bf52-f491412d6fb0 with port d887f6f0-a695-42ba-8de4-859a60d6d2f6: Resource not found 
ERROR   on ../../../../../../tmp/openshift-install-380596170/topology/private-network.tf line 84, in resource "openstack_networking_floatingip_associate_v2" "service_fip": 
ERROR   84: resource "openstack_networking_floatingip_associate_v2" "service_fip" { 
FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply using Terraform 

real	2m13.242s
user	0m40.423s
sys	0m3.888s

Expected results:
No error and floating IP attached to api node.

--- Additional comment from asimonel on 2019-07-30 15:22:52 UTC ---

Further to this we see it happening like this:

We pre-allocate an FIP in openstack as usual:

openstack floating ip create --floating-ip-address IP public

We then add that FIP to lbFloatingIP in install-config.yaml

We then install and this results in the error listed above.

However, if we leave the lbFloatingIP line out of install-config.yaml we get past the error; however we need to manually assign the preallocated FIP to the API node for the install to continue.

It seems like the presence of lbFloatingIP in install-config.yaml is triggering the error but we still need the FIP assigned to allow the install to work.

Comment 4 David Sanz 2020-06-29 12:19:04 UTC
Verified on 4.2.0-0.nightly-2020-06-27-103828

Note You need to log in before you can comment on or make changes to this bug.