-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
3
-
None
-
None
-
OTA 275, OTA 277, OTA 278
This card extend the CI coverage for the new rule that got accepted recently.
A component in a cluster with less than 250 nodes must complete a version change within a limited period of time: 90 minutes for Machine Config Operator and 20 minutes for others.
DoD:
- An test existing in o/origin that covers the above rule.
- (After soaking 1week?) Open bugs for the COs that violates the rule and add them as exceptions for the test.
For grooming:
An idea for implementation is to check Failing=Unknown in the condition of ClusterVersion's condition. Currently, it is close to the above rule, with the difference of limit=30m (instead of 20m). We may tighten it to 20m in CVO's code if realistic.
- is related to
-
OTA-362 CI: fail update suite if any ClusterOperator go Available=False
-
- Closed
-
- links to