The upgrade test was running a service load balancer verification that ensured upgrades preserved reachability, but it provided insufficient alerting and debug to narrow down upgrade failures and assign probable cause. In addition, the test failed to verify reuse of connections vs newly created connections. Finally, we don't explicitly measure API reachability during upgrade. Add an e2e test for upgrade that verifies all of these conditions and backport it to 4.2 to ensure we are sufficiently certain about the guarantees we provide to end users.
The code change looks good, and seems to do what this bug requests.
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