-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OTA-1478 add 4.20 ota jobs #65512
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
base: master
Are you sure you want to change the base?
OTA-1478 add 4.20 ota jobs #65512
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dis016 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold for review and rehearse jobs |
release: | ||
architecture: multi | ||
channel: candidate | ||
version: "4.21" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this will break 4.20 ci tests in the job config, could you trigger some tests under openshift-verification-tests-main__ota-multi-stable-4.20-upgrade-from-stable-4.19.yaml
to have a try?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dis016 what are your follow up actions to address this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dis016 I think you can create a new JIRA card to track the work which requires OCP 4.21, and implement jobs only when there are OCP 4.21 payloads.
For this PR, you can just remove this version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue was introduced by #58136. Dropping it when enable 4.20 test and then add it back someday sounds a workaround. But the issue will come back again when enable 4.21/4.22.. test.
Personally I think it will bring the team endless maintenance work. cc @JianLi-RH to consider fixing the test from code level. Actually 4.21 is not an upgrade target for path 4.20.0 -> 4.20.latest -> 4.21, which is not required to be configured in job level. We should rely on a long-term resolution to reduce team's maintenance work.
/pj-rehearse periodic-ci-openshift-verification-tests-main-ota-multi-stable-4.20-upgrade-from-stable-4.19-azure-ipi-amd-mixarch-f28 |
@dis016: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-verification-tests-main-ota-multi-stable-4.20-upgrade-from-stable-4.19-azure-ipi-amd-mixarch-f28 |
@dis016: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-verification-tests-main-ota-multi-stable-4.20-upgrade-from-stable-4.19-azure-ipi-amd-mixarch-f28 |
@dis016: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-verification-tests-main-ota-multi-stable-4.20-upgrade-from-stable-4.19-azure-ipi-amd-mixarch-f28 |
@dis016: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@dis016: The following tests failed, say
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. |
relative: 1 | ||
version_bounds: | ||
lower: 4.20.0-0 | ||
stream: 4-stable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, the stream should be 4-dev-preview
.
commands: echo "${INTERMEDIATE_RETARGET}" > ${SHARED_DIR}/upgrade-edge | ||
dependencies: | ||
- env: INTERMEDIATE_RETARGET | ||
name: release:intermediate1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you use intermediate1 in gcp-ipi-retarget-f28
, then the tests is duplicate with baremetal-ipi-retarget-f28
.
But anyway, you can temporarily using intermediate1, but don't forget update it to intermediate2 when there are OCP 4.21 payloads.
intermediate1 meant to test: 4.20.0 -> 4.20.n -> 4.20.(n+1)
but intermediate2 meant to test: 4.20.0 -> 4.20.latest -> 4.21
relative: 1 | ||
version_bounds: | ||
lower: 4.20.0-0 | ||
stream: 4-stable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, the stream should be 4-dev-preview
.
commands: echo "${INTERMEDIATE_RETARGET}" > ${SHARED_DIR}/upgrade-edge | ||
dependencies: | ||
- env: INTERMEDIATE_RETARGET | ||
name: release:intermediate1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment in below file.
OTA-1478 add 4.20 ota jobs
/cc @JianLi-RH @jiajliu @jhou1