Bug 1880383

Summary: Cluster destroy hanging when svc of LB type was created on a FIP less installation
Product: OpenShift Container Platform Reporter: Maysa Macedo <mdemaced>
Component: NetworkingAssignee: Maysa Macedo <mdemaced>
Networking sub component: kuryr QA Contact: GenadiC <gcheresh>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: medium CC: bbennett, ltomasbo, rlobillo
Version: 4.6   
Target Milestone: ---   
Target Release: 4.6.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: 2020-10-27 16:42:21 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:

Description Maysa Macedo 2020-09-18 11:46:03 UTC
Description of problem:

When a fip less installation happened with Kuryr and a Service of Load Balancer type was created, a Floating ip gets associated to the load balancer. The clean-up of the custom router would fail due to the subnet being associated to a fip.


DEBUG Removing Subnet "83e513d0-02b3-4f06-899c-37a1e302e3cf" from Router "1142117d-5369-41bf-a1f7-613d9ac3796f" failed: Expected HTTP response code [200] when accessing [PUT https://10.46.44
.75:13696/v2.0/routers/1142117d-5369-41bf-a1f7-613d9ac3796f/remove_router_interface], but got 409 instead
{"NeutronError": {"type": "RouterInterfaceInUseByFloatingIP", "message": "Router interface for subnet 83e513d0-02b3-4f06-899c-37a1e302e3cf on router 1142117d-5369-41bf-a1f7-613d9ac3796f cann
ot be deleted, as it is required by one or more floating IPs.", "detail": ""}} 
DEBUG Exiting removal of interfaces from custom router


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Trigger a fip less installation with Kuryr (creating a custom router before)
2. Create a service of Load Balancer type.
3. Destroy the ocp cluster

Actual results:


Expected results:


Additional info:

Comment 1 rlobillo 2020-09-23 14:37:43 UTC
Verified on 4.6.0-0.nightly-2020-09-23-022756 over RHOS-16.1-RHEL-8-20200903.n.0

Test detailed on https://bugzilla.redhat.com/show_bug.cgi?id=1874457

Comment 4 errata-xmlrpc 2020-10-27 16:42:21 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 (OpenShift Container Platform 4.6 GA Images), 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:4196