Bug 1841846 - kuryrnetworks blocking namespace deletion and making kuryr-controller to crash
Summary: kuryrnetworks blocking namespace deletion and making kuryr-controller to crash
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.0
Assignee: Luis Tomas Bolivar
QA Contact: GenadiC
URL:
Whiteboard:
Depends On:
Blocks: 1843463
TreeView+ depends on / blocked
 
Reported: 2020-05-29 16:05 UTC by Luis Tomas Bolivar
Modified: 2020-10-27 16:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:01:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 251 0 None closed Bug 1841846: Ensure kuryrnetwork CRs without status can be deleted 2020-08-03 09:29:31 UTC
OpenStack gerrit 731797 0 None MERGED Ensure kuryrnetwork CRs without status can be deleted 2020-08-03 09:29:31 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:02:28 UTC

Description Luis Tomas Bolivar 2020-05-29 16:05:38 UTC
If a namespace deletion event gets triggered before kuryrnetwork handler started handling the kuryrnetwork CRD status population, kuryr will only trigger the last update on the kuryrnetwork CRD object and will only execute the on_finalize event. 

Right now that method expect the status field to be there and makes the kuryr-controller crash, leaving the namespace deletion blocked since the kuryrnetwork CRD cannot get the finalizer removed

Comment 7 errata-xmlrpc 2020-10-27 16:01:56 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


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