-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
8
-
False
-
None
-
False
-
-
-
ETCD Sprint 255, ETCD Sprint 256, ETCD Sprint 257, ETCD Sprint 258, ETCD Sprint 259
The quorum checker starts to become very difficult to maintain and we're having a lot more problems with concurrent controllers as identified in OCPBUGS-31849.
To avoid plastering the code in all places where a revision rollout could happen, we should invert the control and tell the revision controller when we do not want to have a rollout at all.
Links to some of the discussions:
- https://docs.google.com/document/d/1BuIvDaTG-GCPWpiJDHYv-sxyEGyE_vS3BC_quP-qPqw/edit#heading=h.3g190z8b529d
- https://redhat-internal.slack.com/archives/CC3CZCQHM/p1722951904692149
AC:
Add precondition to the revision controller - this would halt the whole revision process
- introduce a callback true/false to skip the creation of new revision if the quorum is about to be violated.
- duplicates
-
OCPBUGS-31849 cert signer controller race condition with quorum checker
- Closed
- is cloned by
-
ETCD-639 E2E- skip static pod rollouts when quorum is not safe
- Closed
- links to
(3 links to)