-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
3
-
None
-
None
-
Weedle Sprint 283
Ensure the cluster-olm-operator meets these requirements:
*New changed API rule
A component must not report Available=False or Degrade=True during the course of a normal upgrade.
A version change is a config change. Operators must go Progressing=True when transitioning between versions.
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.
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.
If any rule is not met, please make another story under the same epic to capture any work necessary to bring the cluster-olm-operator in line with these requirements.
- is related to
-
OCPBUGS-62635 cluster operator olm reported Progressing=True with reason=CatalogdDeploymentCatalogdControllerManager_Deploying or reason=OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying for a node reboot
-
- ASSIGNED
-
-
OCPBUGS-62517 ClusterOperator olm goes Available=False with reason=CatalogdDeploymentCatalogdControllerManager_Deploying or reason=OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying during updates
-
- POST
-
-
OCPBUGS-65623 Cluster Operator olm did not report Progressing=True during a cluster update
-
- POST
-
-
OCPBUGS-65581 Component Readiness: [OLM] [Operator] test regressed: clusteroperator/marketplace must go Progressing=True during an upgrade test
-
- Verified
-