-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
None
-
None
-
None
-
OTA 277, OTA 278
This card extends the CI coverage for the new rule that got accepted recently.
Operators should not report Progressing only because DaemonSets owned by them are adjusting to a new node from cluster scaleup or a node rebooting from cluster upgrade.
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
- scaleup/down: e..g, in this machine-scaling testing, we cross-check the set of Progressing=False COs before and after the scale up/down, the set cannot become smaller.
- reboot a worker: find/create a machine-reboot testing, we cross-check the set of Progressing=False COs as the above.
- is related to
-
OCPBUGS-62635 cluster operator olm reported Progressing=True with reason=CatalogdDeploymentCatalogdControllerManager_Deploying or reason=OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying for a node reboot
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- ASSIGNED
-
-
-
- POST
-
-
-
- POST
-
-
-
- Closed
-
- links to