Skip to content

OCPBUGS-85516: Update openshift-test-private commit#6664

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
kasturinarra:local-4.20
May 14, 2026
Merged

OCPBUGS-85516: Update openshift-test-private commit#6664
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.20from
kasturinarra:local-4.20

Conversation

@kasturinarra
Copy link
Copy Markdown
Contributor

Updating openshift-test-private commit so that the fix here is included https://github.com/openshift/openshift-tests-private/pull/29899

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c8ab6b5e-6935-4f0f-9a97-713c98ce6af1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@kasturinarra kasturinarra changed the title Update openshift-test-private commit USHIFT-6946: Update openshift-test-private commit May 13, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 13, 2026

@kasturinarra: This pull request references USHIFT-6946 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 the "4.20.z" version, but no target version was set.

Details

In response to this:

Updating openshift-test-private commit so that the fix here is included https://github.com/openshift/openshift-tests-private/pull/29899

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 requested review from agullon and copejon May 13, 2026 10:22
@kasturinarra
Copy link
Copy Markdown
Contributor Author

/retest

@agullon
Copy link
Copy Markdown
Contributor

agullon commented May 13, 2026

/lgtm
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

/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 May 13, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, 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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2026
@kasturinarra
Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@kasturinarra
Copy link
Copy Markdown
Contributor Author

/retest

@kasturinarra
Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-periodic-arm ci/prow/e2e-aws-tests-periodic ci/prow/e2e-aws-tests-bootc-periodic

overriding as the failure is not related to the PR.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

@kasturinarra: kasturinarra unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-periodic-arm ci/prow/e2e-aws-tests-periodic ci/prow/e2e-aws-tests-bootc-periodic

overriding as the failure is not related to the PR.

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.

@pacevedom
Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-aws-tests-bootc-periodic
/override ci/prow/e2e-aws-tests-bootc-periodic-arm
/override ci/prow/e2e-aws-tests-periodic
/override ci/prow/e2e-aws-tests-periodic-arm

Unrelated failures.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

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

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-periodic
/override ci/prow/e2e-aws-tests-bootc-periodic-arm
/override ci/prow/e2e-aws-tests-periodic
/override ci/prow/e2e-aws-tests-periodic-arm

Unrelated failures.

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.

@kasturinarra
Copy link
Copy Markdown
Contributor Author

kasturinarra commented May 14, 2026

/label backport-risk-assessed

1 similar comment
@kasturinarra
Copy link
Copy Markdown
Contributor Author

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 14, 2026
@kasturinarra kasturinarra changed the title USHIFT-6946: Update openshift-test-private commit [USHIFT-6946] [OCPBUGS-85516]: Update openshift-test-private commit May 14, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@kasturinarra: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Updating openshift-test-private commit so that the fix here is included https://github.com/openshift/openshift-tests-private/pull/29899

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.

@kasturinarra kasturinarra changed the title [USHIFT-6946] [OCPBUGS-85516]: Update openshift-test-private commit OCPBUGS-85516: Update openshift-test-private commit May 14, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@kasturinarra: This pull request references Jira Issue OCPBUGS-85516, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Updating openshift-test-private commit so that the fix here is included https://github.com/openshift/openshift-tests-private/pull/29899

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.

@kasturinarra
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@kasturinarra: This pull request references Jira Issue OCPBUGS-85516, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-72360 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-72360 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

Requesting review from QA contact:
/cc @jogeo

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 requested a review from jogeo May 14, 2026 07:27
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

@kasturinarra: 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-periodic 257c780 link true /test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests-bootc-periodic 257c780 link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests-bootc-periodic-arm 257c780 link true /test e2e-aws-tests-bootc-periodic-arm
ci/prow/e2e-aws-tests-periodic-arm 257c780 link true /test e2e-aws-tests-periodic-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 c72ec5b into openshift:release-4.20 May 14, 2026
15 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@kasturinarra: Jira Issue OCPBUGS-85516: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-85516 has been moved to the MODIFIED state.

Details

In response to this:

Updating openshift-test-private commit so that the fix here is included https://github.com/openshift/openshift-tests-private/pull/29899

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.

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.

4 participants