+++ This bug was initially created as a clone of Bug #1777492 +++ 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:
Ran conformance tests. The following failed: [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-cli] Kubectl client [k8s.io] Kubectl logs should be able to retrieve and filter logs [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-network] DNS should provide DNS for services [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-network] DNS should provide DNS for the cluster [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-storage] ConfigMap should be consumable from pods in volume [NodeConformance] [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-storage] Projected downwardAPI should provide container's memory limit [NodeConformance] [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] No restart of the kuryr-controller Using 4.3.0-0.nightly-2019-12-11-073659
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:0062