Created attachment 1679286 [details] ovnkube-master logs Description of problem: Do upgrade with OVN network from 4.4.0-0.nightly-2020-04-15-212458 to 4.5.0-0.nightly-2020-04-15-072621. found the api pod cannot access 172.30.0.1:443 Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-04-15-212458 --> 4.5.0-0.nightly-2020-04-15-072621 How reproducible: always Steps to Reproduce: 1. Check the apiserver pod 2. 3. Actual results: oc get pod -n openshift-apiserver -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES apiserver-5f4b56c785-97zvq 0/1 CrashLoopBackOff 11 41m 10.130.0.4 ip-10-0-132-60.us-east-2.compute.internal <none> <none> apiserver-5f4b56c785-pzxmg 0/1 CrashLoopBackOff 10 40m 10.129.0.13 ip-10-0-157-61.us-east-2.compute.internal <none> <none> apiserver-5f4b56c785-wfmxw 0/1 CrashLoopBackOff 11 41m 10.128.0.17 ip-10-0-16 oc logs apiserver-5f4b56c785-97zvq -n openshift-apiserver Copying system trust bundle F0416 10:03:35.419665 1 cmd.go:72] unable to load configmap based request-header-client-ca-file: Get https://172.30.0.1:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication: dial tcp 172.30.0.1:443: i/o timeout Expected results: Additional info:
OVN master pod with ovnkube-master container is not be working well, see the logs in attachment
Created attachment 1679288 [details] another ovnkube-master pod logs
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:2409