USHIFT-3141: Increase vm boot timeout to 30m in scenarios #3338
Conversation
As the number of VMs increases, so does the time they need to boot in CI. We have had a few timeouts lately with 15m, so we increase it to 30m to avoid having flakes.
openshift-ci-robot
added
the
jira/valid-reference
|
@pacevedom: This pull request references USHIFT-3141 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/cc @ggiguash |
openshift-ci
bot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@pacevedom: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
As the number of VMs increases, so does the time they need to boot in CI. We have had a few timeouts lately with 15m, so we increase it to 30m to avoid having flakes.
Which issue(s) this PR addresses:
Closes #