Bug 1777492

Summary:	Not handled exceptions wrongly cause Kuryr Controller restart
Product:	OpenShift Container Platform	Reporter:	Maysa Macedo <mdemaced>
Component:	Networking	Assignee:	Maysa Macedo <mdemaced>
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	itbrown, ltomasbo
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1777513 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:17:52 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:	1777513

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