Description of problem:
Tracking per-operator fixes for the following related issues static pod node, installer, and revision controllers: https://issues.redhat.com/browse/OCPBUGS-45924 https://issues.redhat.com/browse/OCPBUGS-46372 https://issues.redhat.com/browse/OCPBUGS-48276
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- is cloned by
-
OCPBUGS-48686 [cluster-kube-apiserver-operator] Inconsistent static pod operator statuses after apply migration
-
- Verified
-
-
OCPBUGS-49772 [release-4.18] [cluster-etcd-operator] Inconsistent static pod operator statuses after apply migration
-
- Closed
-
- is depended on by
-
OCPBUGS-49772 [release-4.18] [cluster-etcd-operator] Inconsistent static pod operator statuses after apply migration
-
- Closed
-
- relates to
-
OCPBUGS-45924 Etcd quorum lost during bootstrap because two static pod installers trigger concurrent rollouts
-
- Verified
-
-
OCPBUGS-46372 Static pod node controller can overwrite nodestatuses with stale information
-
- Verified
-
-
OCPBUGS-48276 Static pod revision controller can fail to observe its most recent write and try to decrease latest revision
-
- Verified
-
- links to