Bug 2078875 - OpenShift Installer fail to remove Neutron ports
Summary: OpenShift Installer fail to remove Neutron ports
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: rdobosz
QA Contact: Itzik Brown
URL:
Whiteboard:
: 2060413 (view as bug list)
Depends On:
Blocks: 2083632
TreeView+ depends on / blocked
 
Reported: 2022-04-26 12:02 UTC by rdobosz
Modified: 2022-08-10 11:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:08:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5838 0 None open Bug 2078875: Delete all the ports from tagged Neutron networks. 2022-04-26 12:05:16 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:08:59 UTC

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


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