Skip to content

[release-4.21] USHIFT-6380: Fix OLM test random failures#5971

Merged
openshift-merge-bot[bot] merged 8 commits intoopenshift:release-4.21from
ggiguash:fix-olm-failures-421
Dec 23, 2025
Merged

[release-4.21] USHIFT-6380: Fix OLM test random failures#5971
openshift-merge-bot[bot] merged 8 commits intoopenshift:release-4.21from
ggiguash:fix-olm-failures-421

Conversation

@ggiguash
Copy link
Contributor

Manual cherry-pick of #5942

@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 22, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 22, 2025

@ggiguash: This pull request references USHIFT-6380 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 bug to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.22" instead.

Details

In response to this:

Manual cherry-pick of #5942

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.

@ggiguash
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 22, 2025

@ggiguash: This pull request references USHIFT-6380 which is a valid jira issue.

Details

In response to this:

/jira refresh

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 22, 2025
@kasturinarra
Copy link
Contributor

/lgtm

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

agullon commented Dec 22, 2025

/retest

@agullon
Copy link
Contributor

agullon commented Dec 22, 2025

/override e2e-aws-tests-release
/override e2e-aws-tests-release-arm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@agullon: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-aws-tests-release
  • e2e-aws-tests-release-arm

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-aws-tests
  • ci/prow/e2e-aws-tests-arm
  • ci/prow/e2e-aws-tests-bootc
  • ci/prow/e2e-aws-tests-bootc-arm
  • ci/prow/e2e-aws-tests-bootc-periodic
  • ci/prow/e2e-aws-tests-bootc-periodic-arm
  • ci/prow/e2e-aws-tests-bootc-release
  • ci/prow/e2e-aws-tests-bootc-release-arm
  • ci/prow/e2e-aws-tests-periodic
  • ci/prow/e2e-aws-tests-periodic-arm
  • ci/prow/e2e-aws-tests-release
  • ci/prow/e2e-aws-tests-release-arm
  • ci/prow/images
  • ci/prow/security
  • ci/prow/test-unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-microshift-main-e2e-aws-tests
  • pull-ci-openshift-microshift-main-e2e-aws-tests-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-periodic-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-periodic
  • pull-ci-openshift-microshift-main-e2e-aws-tests-periodic-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-release
  • pull-ci-openshift-microshift-main-e2e-aws-tests-release-arm
  • pull-ci-openshift-microshift-main-images
  • pull-ci-openshift-microshift-main-security
  • pull-ci-openshift-microshift-main-test-unit
  • pull-ci-openshift-microshift-main-verify
  • pull-ci-openshift-microshift-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override e2e-aws-tests-release
/override 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.

@agullon
Copy link
Contributor

agullon commented Dec 22, 2025

/override ci/prow/e2e-aws-tests-release-arm
/override ci/prow/e2e-aws-tests-release

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

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

Details

In response to this:

/override ci/prow/e2e-aws-tests-release-arm
/override ci/prow/e2e-aws-tests-release

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.

@agullon
Copy link
Contributor

agullon commented Dec 22, 2025

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/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 22, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 22, 2025
@openshift-ci-robot
Copy link

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

Details

In response to this:

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/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
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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:
  • OWNERS [agullon,ggiguash,kasturinarra]

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

@agullon
Copy link
Contributor

agullon commented Dec 22, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@ggiguash: 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-release b9fc33e link true /test e2e-aws-tests-release
ci/prow/e2e-aws-tests-release-arm b9fc33e link true /test e2e-aws-tests-release-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 903c000 into openshift:release-4.21 Dec 23, 2025
18 checks passed
@ggiguash ggiguash deleted the fix-olm-failures-421 branch December 23, 2025 18:20
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.

5 participants