Bug 1777492 - Not handled exceptions wrongly cause Kuryr Controller restart
Summary: Not handled exceptions wrongly cause Kuryr Controller restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Maysa Macedo
QA Contact: GenadiC
URL:
Whiteboard:
Depends On:
Blocks: 1777513
TreeView+ depends on / blocked
 
Reported: 2019-11-27 16:15 UTC by Maysa Macedo
Modified: 2020-05-04 11:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1777513 (view as bug list)
Environment:
Last Closed: 2020-05-04 11:17:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 88 0 'None' closed Bug 1777492: Fix not handled exceptions causing Kuryr restarts 2020-03-30 09:47:02 UTC
OpenStack gerrit 695445 0 'None' MERGED Prevent Kuryr restart due to connection issue 2020-03-30 09:47:01 UTC
OpenStack gerrit 695541 0 'None' MERGED Ensure not found exception is ignored when LB is not present 2020-03-30 09:47:01 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:18:16 UTC

Description Maysa Macedo 2019-11-27 16:15:35 UTC 
Description of problem:

A few exceptions were not properly handled wrongly causing a Kuryr-Controller to restart: 
1) When retrying a deletion of a load balancer, the attempt to retrieve it could cause a NotFoundException, which is different than the currently exception being handled ResourceNotFound.
2) When the connection to Keystone is broken the controller is instantly marked as not healthy, when should at least retry a few times the connection before restarting. 

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

OSP 15


How reproducible:


Steps to Reproduce:
1. Run OCP conformance tests 
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Itzik Brown 2020-01-27 14:14:17 UTC 
4.4.0-0.nightly-2020-01-24-141203
Ran the conformance tests.
Haven't encountered the errors mentioned.
Comment 4 errata-xmlrpc 2020-05-04 11:17:52 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, 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:0581
Note You need to log in before you can comment on or make changes to this bug.