This looks like a skew bug between master and kubelet, so we need to treat it special Post rebase Probing container should *not* be restarted with a non-local redirect http liveness probe [Suite:openshift/conformance/parallel] [Suite:k8s] 4m24s flakes heavily when masters are 4.2 and rhcos is 4.1 kubelet. This is not a new test so my assumption is something is broken between 1.13 kubelet and 1.14 masters that we need to know about https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/182#openshift-tests-k8sio-probing-container-should-not-be-restarted-with-a-non-local-redirect-http-liveness-probe-suiteopenshiftconformanceparallel-suitek8s fail [k8s.io/kubernetes/test/e2e/common/container_probe.go:524]: May 18 23:26:13.408: pod container-probe-1387/liveness-http-redirect - expected number of restarts: 0, found restarts: 6 This blocks upgrade to 4.2
This bug may not be deferred from 4.2 without identifying why this fails. Disabled in https://github.com/openshift/origin/pull/22865
This test was new in kubernetes 1.14 and does not tolerate skew between the e2e from 4.2 and kubelet running at 4.1 https://github.com/kubernetes/kubernetes/pull/75416
https://github.com/openshift/origin/pull/23461
This test is now passing in recent CI tests. https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/2624/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.2/2616/
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-2019:2922