Hide Forgot
Seeing a decent number of flakes with "Failed to get secret openshift-kube-apiserver/etcd-client-1: secrets \"etcd-client-1\" not found" https://search.svc.ci.openshift.org/?search=Failed+to+get+secret+openshift-kube-apiserver%2Fetcd-client-1&maxAge=24h&context=2&type=all such as https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/482/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/481/ https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/480/
https://github.com/openshift/cluster-kube-apiserver-operator/pull/451 https://github.com/openshift/cluster-kube-controller-manager-operator/pull/244 https://github.com/openshift/cluster-kube-scheduler-operator/pull/123 All merged, moving to QA.
The bug reported failure for test "[Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes". Checked latest accepted payloads like 4.1.0-0.nightly-2019-05-07-233329 (https://openshift-release.svc.ci.openshift.org/releasestream/4.1.0-0.nightly/release/4.1.0-0.nightly-2019-05-07-233329): Its logs https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.1/166 showed it passed that test.
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:0758