-
Bug
-
Resolution: Done
-
High
-
None
-
OSC 1.11
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
Blanc #4
-
Important
-
8
Description
We get multiple timeouts when we apply a deployment.
waitForDeployment() has a loop to look at the readyReplicas vs specReplicas defined in the deployment. The timeout is resSnoose (300s) and this is not always enough time, especially for kata-remote or many replicas.
resSnoose is also used for deleteOperator() for csv and sub deletion and check if kataconfig exists podSnooze is 600s.
waitForDeployment() should have a longer timeout and it should add for each replica added