-
Bug
-
Resolution: Won't Do
-
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 in the single node jobs is that we're still hitting a lot of cases where the kube-controller-manager static pod isn't appearing within the expected ~3 minutes.
Here are some examples from the recent SNO presubmits:
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29967/pull-ci-openshift-origin-main-e2e-aws-ovn-single-node/1942387062007140352
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29956/pull-ci-openshift-origin-main-e2e-aws-ovn-single-node/1942108174068748288
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_cluster-authentication-operator/740/pull-ci-openshift-cluster-authentication-operator-master-e2e-aws-single-node/1941069172226134016
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29934/pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade/1940832177205809152
- clones
-
OCPBUGS-43631 Static pod controller pods sometimes fail to start [kube-controller-manager]
-
- Closed
-
- is cloned by
-
OCPBUGS-59153 Static pods should start after being created [openshift-etcd]
-
- New
-
-
OCPBUGS-59151 Static pods should start after being created [SNO] [kube-apiserver]
-
- Closed
-