Created attachment 1688801 [details] installer log Description of problem: Sometimes the IPI installer fails with: level=error msg="Error: Error associating openstack_networking_floatingip_associate_v2 floating_ip f9c0533c-6069-4948-a3de-b8e09b9b79d4 with port 58a25d7a-e443-4901-8b48-3d6c505fe247: Resource not found" But both floating ip and port exist: FIP: f9c0533c-6069-4948-a3de-b8e09b9b79d4 | 10.0.105.110 | None | None | d655dcd0-b593-439c-997b-aa5bc8c03a3a | 0d9514d7da8441a199c33a296e541a7a | Port: | 58a25d7a-e443-4901-8b48-3d6c505fe247 | fbr-43-s9pjg-api-port | fa:16:3e:6d:5b:ab | ip_address='192.168.0.5', subnet_id='2008a184-6073-43f8-b70c-1e2b35841aa8' | DOWN | Version-Release number of the following components: OCP 4.3.z OCP 4.4.z How reproducible: Sometimes. It seems it happens when the OpenStack is under heavy load Steps to Reproduce: 1. get installer 2. create FIP for API: openstack --os-cloud rhos_cloud floating ip create --description fbr-43-api -f value -c floating_ip_address provider_net_cci_9 3. edit install-config.yaml (attached) 4. run installer: ./openshift-install --log-level debug create cluster --dir /home/jenkins/agent/workspace/install-ocp-ipi/openshift/cluster-installation/psi/fbr-43 Actual results: level=error msg="Error: Error associating openstack_networking_floatingip_associate_v2 floating_ip f9c0533c-6069-4948-a3de-b8e09b9b79d4 with port 58a25d7a-e443-4901-8b48-3d6c505fe247: Resource not found" Expected results: No errors. Additional info: install-config.yaml and installer log attached. Both FIP and port exist when checked after the failure.
Created attachment 1688802 [details] install config yaml
Could it be that your OpenStack cloud is a bit light on the specs? In that case it could be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1734460.
This issue is visible in RH PSI OpenStack which I don't control. It's used by many RH teams and sometimes gets overloaded. It would be nice to follow up with PSI OpenStack admins if the cause is on the OpenStack side.
Adding the testblocker , since failed to set up the clusters for IPI on OSP with kuryr test due to this issue.
Also failed on UPI on OSP with kuryr
*** This bug has been marked as a duplicate of bug 1734460 ***