upgrade: extend upgrade duration to 105mins on AWS #26230
Conversation
Some upgrades finish slightly above 90m limit: * https://search.ci.openshift.org/?search=sig-cluster-lifecycle.*cluster+upgrade+should+complete+in+&maxAge=96h0m0s&context=3&type=junit&name=aws&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job All taking up to 105m.
vrutkovs
changed the title
openshift-ci
bot
added
bugzilla/severity-high
|
@vrutkovs: This pull request references Bugzilla bug 1970975, which is invalid:
Comment DetailsIn 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 kubernetes/test-infra repository. |
vrutkovs
changed the title
|
@vrutkovs: No Bugzilla bug is referenced in the title of this pull request. DetailsIn 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 kubernetes/test-infra repository. |
openshift-ci
bot
removed
bugzilla/severity-high
|
/cherrypick release-4.8 |
|
@vrutkovs: once the present PR merges, I will cherry-pick it on top of release-4.8 in a new PR and assign it to you. DetailsIn 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 kubernetes/test-infra repository. |
|
/retest |
|
/lgtm Any way to test with aws-upgrade? Unhold at will. |
openshift-ci
bot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts, vrutkovs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
lgtm
|
/retest |
|
/test e2e-aws-upgrade |
|
/test e2e-gcp-upgrade |
|
/retest |
5 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/hold cancel Added e2e-aws-upgrade test, lets leave it running over the weekend |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest Please review the full test history for this PR and help us cut down flakes. |
7 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@vrutkovs: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@vrutkovs: new pull request created: #26252 DetailsIn 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 kubernetes/test-infra repository. |
5 participants
Some upgrades finish slightly above 90m limit - https://search.ci.openshift.org/?search=sig-cluster-lifecycle.*cluster+upgrade+should+complete+in+&maxAge=96h0m0s&context=3&type=junit&name=aws&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
Longest so far seems to be aws-ovn-upgrade - 104.34.
test upgrade 4.8.0-rc.0 https://github.com/openshift/origin/pull/26230 aws
This would bump AWS timeout to 105m until this is thoroughly investigated