-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
No
-
None
-
None
-
Rejected
-
None
-
In Progress
-
None
-
None
-
None
-
None
-
None
-
None
For historical context, see the discussion in https://issues.redhat.com/browse/OCPBUGS-43631.
One thing we're observing across jobs, but occasionally in the single-node jobs is that the openshift-etcd static pod doesn't start before it's three minute timeout. Here are a collection of job runs exhibiting the issue:
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-network-operator/2731/pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-single-node/1942913639249874944
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-etcd-operator/1443/pull-ci-openshift-cluster-etcd-operator-main-e2e-aws-disruptive-ovn/1942900069606887424
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-etcd-operator/1443/pull-ci-openshift-cluster-etcd-operator-main-e2e-aws-disruptive/1942900069569138688
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-etcd-operator/1443/pull-ci-openshift-cluster-etcd-operator-main-e2e-gcp-disruptive/1942900095418634240
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-etcd-operator/1443/pull-ci-openshift-cluster-etcd-operator-main-e2e-gcp-disruptive-ovn/1942900097025052672
- clones
-
OCPBUGS-59150 Static pods should start after being created [SNO] [kube-controller-manager]
-
- Closed
-
- duplicates
-
OCPBUGS-57117 [sig-node] static pods should start after being created
-
- Closed
-
- is related to
-
OCPBUGS-60884 OpenShift SNO - kube-apiserver took 1 hour to recover after cert rotation
-
- ASSIGNED
-