Floating IP specified with lbFloatingIP in install-config.yaml fails to attach to master node causing install to fail in OpenShift 4.x on OpenStack 13

Solution Verified - Updated -

Issue

Floating IP specified with lbFloatingIP in install-config.yaml fails to attach to master node causing install to fail in OpenShift 4.x on OpenStack 13

During the OpenShift on OpenStack install process a floating IP is being attached to the bootstrap node. It is failing to attach the floating IP specified in install-config.yaml to the API port.

ERROR                                              
ERROR Error: Error associating openstack_networking_floatingip_associate_v2 floating_ip b619b6e7-7ed6-4e5d-9195-926ee673989d with port 3b74e394-1099-4475-85ae-1f22fbf8b4c8: Resource not found 
ERROR                                              
ERROR   on ../../../tmp/openshift-install-624216800/topology/private-network.tf line 122, in resource "openstack_networking_floatingip_associate_v2" "api_fip": 
ERROR  122: resource "openstack_networking_floatingip_associate_v2" "api_fip" { 
ERROR                                              
ERROR                                              
FATAL failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply using Terraform 

Environment

Red Hat OpenShift Container Platform 4.2
Red Hat OpenShift Container Platform 4.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In