-
Notifications
You must be signed in to change notification settings - Fork 2k
jobs: extend 4.6 -> 4.7 -> 4.8 upgrade timeout to 8hrs #21355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jobs: extend 4.6 -> 4.7 -> 4.8 upgrade timeout to 8hrs #21355
Conversation
596e5bf to
a6d3deb
Compare
|
/retest Failed on 4.3 -> 4.4 leg |
061edf7 to
70444cf
Compare
|
/retest |
b272e29 to
42b0d34
Compare
|
/retest |
e5356e2 to
8083065
Compare
|
Not sure why stable-initial install doesn't complete /retest |
|
/retest |
1 similar comment
|
/retest |
c62bbd8 to
7818fd1
Compare
|
/retest |
1 similar comment
|
/retest |
d122e2e to
02d3b6d
Compare
|
/retest |
10488cc to
8e54958
Compare
|
/retest |
|
/approve |
|
Issues in openshift/release go stale after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
80d46cf to
a171073
Compare
ce41d63 to
4977520
Compare
These tests are sequential upgrades to ensure born-in-4.x clusters can be upgraded to 4.8. Disruption tests are skipped, prowjob timeout is extended to 8 hours
4977520 to
0498c82
Compare
|
/cc @wking |
|
Stale issue in openshift/release rot after 15d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
/retest |
|
/lgtm Looks good to me. Would be nice to have a rehearsal confirming it works before pulling the hold, but if it's to hard to get the ancient versions to install, I'm fine landing this first and adjusting later if necessary. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrutkovs, wking 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 |
|
/hold cancel Lets run them live for a few weeks, we might want to move them to never-stable if these never pass |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@vrutkovs: The following tests 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. |
|
@vrutkovs: Updated the following 3 configmaps:
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. |
TODO:
This would make it send a new report, so that we could see the result in the Superset.
UPD: CI runs are preconfigured to run snapshots every 10 mins, which is enough for post section to trigger this
Requires openshift/ci-tools#2294 to pass generated job checker