You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workloads need to make sure to wait till all the objects created by it are terminated to determine if the test passed/failed since we observed in CI runs that the projects were stuck in terminated meaning the cluster is unhealthy and the next test in the pipeline run is no longer valid/has high chances of failure.
It might be difficult to use --wait=true during project deletion as it's a serial operation in case of workloads creating thousands of projects like Master Vertical and Namespaces per cluster but we can start by making sure the workloads which creates < 100 projects use --wait=true during the cleanup for example HTTP workload - https://github.com/openshift-scale/workloads/blob/master/workloads/files/workload-http-script-cm.yml#L621.
The text was updated successfully, but these errors were encountered:
The workloads need to make sure to wait till all the objects created by it are terminated to determine if the test passed/failed since we observed in CI runs that the projects were stuck in terminated meaning the cluster is unhealthy and the next test in the pipeline run is no longer valid/has high chances of failure.
It might be difficult to use --wait=true during project deletion as it's a serial operation in case of workloads creating thousands of projects like Master Vertical and Namespaces per cluster but we can start by making sure the workloads which creates < 100 projects use --wait=true during the cleanup for example HTTP workload - https://github.com/openshift-scale/workloads/blob/master/workloads/files/workload-http-script-cm.yml#L621.
The text was updated successfully, but these errors were encountered: