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
Currently, the workload is kicked only when all hosted clusters are created. However, we have seen that it's highly likely that one or more HC installs fails leading to the entire test failing and having to cleanup, and rerun.
It would be good to have a flag to consume toleration for failure like (10%) and as long as the number of Hosted Clusters that have not been created after a timeout is less than that, the script should proceed to creating the workload and cleaning up after that.
The text was updated successfully, but these errors were encountered:
We can enhance wrapper to have 2 ways to start e2e
current way of when all the clusters moved to ready state
Additionally make wrapper listen on a socket (or a file) and wait for user command like "start_e2e" to start e2e before above condition is met (i.e before all clusters are ready). In this way user can ask wrapper whenever he wants the e2e to get started for example, start e2e when he sees 50 clusters are ready during 80HC testing.
Currently, the workload is kicked only when all hosted clusters are created. However, we have seen that it's highly likely that one or more HC installs fails leading to the entire test failing and having to cleanup, and rerun.
It would be good to have a flag to consume toleration for failure like (10%) and as long as the number of Hosted Clusters that have not been created after a timeout is less than that, the script should proceed to creating the workload and cleaning up after that.
The text was updated successfully, but these errors were encountered: