CNO currently does not log anything if leader election fails / goes unexpectedly. In particular, the IPv6 IPI job is currently failing in weird ways and there is no info in the logs explaining why
@Dan Could you give any advice how to make CNO leader election fails to verify this bug?
The CNO pod that becomes leader should now log "Became the leader", while other CNO pods will log "Not the leader. Waiting". (The particular IPv6 jobs I added this in order to debug are now failing with a different error so this isn't helping there.)
Thanks Dan Winship There should be only one pod for CNO. $ oc get pod -n openshift-network-operator NAME READY STATUS RESTARTS AGE network-operator-7d49f7f9d5-v54zr 1/1 Running 0 89m >> while other CNO pods will log "Not the leader. Waiting". what's the mean I can see the "became the leader" in above pod #oc logs network-operator-7d49f7f9d5-v54zr -n openshift-network-operator | grep -i "Became the leader" 2020/09/09 05:38:24 Became the leader.
> There should be only one pod for CNO. ah, well, that's something else that was wrong with the other cluster then > I can see the "became the leader" in above pod > > #oc logs network-operator-7d49f7f9d5-v54zr -n openshift-network-operator | > grep -i "Became the leader" > 2020/09/09 05:38:24 Became the leader. Then the PR worked
Thanks the information @Dan move this bug to verified.
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.6 GA Images), 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:4196