+++ This bug was initially created as a clone of Bug #2080876 +++
Description of problem:
Before registering OVN northd metrics, we check to see if ovnkube
master is co-located on the same node and repeatedly check if it
is present because ovnkube node may start before ovnkube master.
This repeated checking only causes one error mode to occur which
is a timeout error and this is incorrectly logged as an error
confusing the user.
The only failure path to occur within 'checkPodRunsOnGivenNode' can
be seen with increased log level.
To verify this:
1. Grep the logs of the ovnkube-node container that isn't on a control plane node for the Error message 'Timed out while checking if OVNKube Master Pod runs'. You should not get a result.
2. Grep the logs of the ovnkube-node container that isn't on a control plane node for the Info message 'Not registering OVN North Metrics because OVNKube Master Pod was not found running on this'. You should get a result.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Grep the logs of the ovnkube-node container that isn't on a control plane node for the Error message 'Timed out while checking if OVNKube Master Pod runs'.
Not error message but an Info message
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.10.14 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.