Hide Forgot
Verified on 4.6.0-0.nightly-2020-10-28-001707 over OSP16.1 with OVN-Octavia (RHOS-16.1-RHEL-8-20201007.n.0) After 2 days of cluster up, no kuryr-cni pod went to CrashLoopBackOff: [stack@undercloud-0 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-28-001707 True False 2d1h Cluster version is 4.6.0-0.nightly-2020-10-28-001707 [stack@undercloud-0 ~]$ oc get pods -n openshift-kuryr NAME READY STATUS RESTARTS AGE kuryr-cni-962bd 1/1 Running 1 2d2h kuryr-cni-lfkbm 1/1 Running 4 2d1h kuryr-cni-scr8g 1/1 Running 1 2d2h kuryr-cni-t5hzc 1/1 Running 1 2d2h kuryr-cni-x7bch 1/1 Running 8 2d1h kuryr-cni-x9b42 1/1 Running 3 2d1h kuryr-controller-598d4bf657-6gs9g 1/1 Running 5 2d2h NP and conformance tests run with expected results.
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.3 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. https://access.redhat.com/errata/RHBA-2020:4339