Skip to content

[release-4.21] USHIFT-6356: Disable scenarios targeting Y-2 upgrade paths on odd versions#5900

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
agullon:USHIFT-6356
Dec 14, 2025
Merged

[release-4.21] USHIFT-6356: Disable scenarios targeting Y-2 upgrade paths on odd versions#5900
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
agullon:USHIFT-6356

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Dec 13, 2025

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2025

@agullon: This pull request references USHIFT-6356 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 13, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 13, 2025
@agullon agullon changed the base branch from main to release-4.21 December 13, 2025 10:38
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2025

@agullon: This pull request references USHIFT-6356 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

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.

@agullon agullon changed the title [release-4.21] USHIFT-6356: remove y-2 upgrade path scenarios for Release Testing [release-4.21] USHIFT-6356: Disable scenarios targeting Y-2 upgrade paths on odd versions Dec 13, 2025
@ggiguash
Copy link
Contributor

This PR is about unnecessary test removal to ease the CI burden and increase stability.
The failures are not related to the changes.
/override ci/prow/e2e-aws-tests-bootc-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 14, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-arm, ci/prow/e2e-aws-tests-bootc-release, ci/prow/e2e-aws-tests-bootc-release-arm, ci/prow/e2e-aws-tests-release, ci/prow/e2e-aws-tests-release-arm

Details

In response to this:

This PR is about unnecessary test removal to ease the CI burden and increase stability.
The failures are not related to the changes.
/override ci/prow/e2e-aws-tests-bootc-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-release-arm

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.

@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/label jira/valid-bug
/lgtm
/verified by ci

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 14, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 14, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/lgtm
/verified by ci

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 14, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 14, 2025

@agullon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-tests-bootc-release 96ce0ae link true /test e2e-aws-tests-bootc-release
ci/prow/e2e-aws-tests-bootc-release-arm 96ce0ae link true /test e2e-aws-tests-bootc-release-arm
ci/prow/e2e-aws-tests-release 96ce0ae link true /test e2e-aws-tests-release
ci/prow/e2e-aws-tests-release-arm 96ce0ae link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-bootc-arm 96ce0ae link true /test e2e-aws-tests-bootc-arm

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 000aa85 into openshift:release-4.21 Dec 14, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants