Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2078875

Summary:	OpenShift Installer fail to remove Neutron ports
Product:	OpenShift Container Platform	Reporter:	rdobosz
Component:	Networking	Assignee:	rdobosz
Networking sub component:	kuryr	QA Contact:	Itzik Brown <itbrown>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	itbrown, m.andre, mdemaced, mdulko
Version:	4.11	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:08:24 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:
Bug Depends On:
Bug Blocks:	2083632

Description rdobosz 2022-04-26 12:02:56 UTC

Description of problem:

Sometimes it happens, that due to Neutron slowness, we may end up with several ports being created inside Kuryr created network, while in a state DOWN and without the tag which indicates service who created it. That means, OpenShift installer cannot successfully remove such Neutron networks because of existing resources (ports in this case).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Maysa Macedo 2022-05-03 12:02:18 UTC

*** Bug 2060413 has been marked as a duplicate of this bug. ***

Comment 4 Martin André 2022-05-10 11:37:11 UTC

According to the duplicate bug https://bugzilla.redhat.com/show_bug.cgi?id=2060413 this is at least present in 4.10. How far do we need to backport this fix? Could you set the Version field accordingly?

Comment 8 Itzik Brown 2022-05-11 19:17:19 UTC

Verified with
4.11.0-0.nightly-2022-05-11-054135
RHOS-16.2-RHEL-8-20220311.n.1

Steps:
1. Created deployment in its own namespace
   $ oc new-project demo2
   $ oc create deployment  --image quay.io/kuryr/demo demo2
2. Created two ports manually in the newly created neutron network
    $ openstack port create --network demo2 port2-2
    $ openstack port create --network demo2 port2-2
3. Deleted ns 
    $ oc delete ns demo2

Deletion tool less than 30 seconds

Comment 10 Itzik Brown 2022-06-01 14:56:26 UTC

Did the following:
Steps:
1. Created deployment in its own namespace
   $ oc new-project demo2
   $ oc create deployment  --image quay.io/kuryr/demo demo2
2. Created two ports manually in the newly created neutron network
    $ openstack port create --network demo2 port2-1
    $ openstack port create --network demo2 port2-2
3. Destroyed the cluster 
4. Verified the resources are removed , the ports port2-1 , port2-2 included 

Used 4.11.0-0.nightly-2022-05-25-193227

Comment 12 errata-xmlrpc 2022-08-10 11:08:24 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069