Skip to content

NO-ISSUE: rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64 - #7221

Merged
openshift-merge-bot[bot] merged 12 commits into
openshift:release-5.0from
eslutsky:rebase-release-5.0-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18_arm64-2026-08-18
Aug 21, 2026
Merged

NO-ISSUE: rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64#7221
openshift-merge-bot[bot] merged 12 commits into
openshift:release-5.0from
eslutsky:rebase-release-5.0-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18_arm64-2026-08-18

Conversation

@eslutsky

@eslutsky eslutsky commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

running rebase manually:

./scripts/auto-rebase/rebase.sh to registry.ci.openshift.org/ocp/release-5:5.0.0-0.nightly-2026-08-18-203845 registry.ci.openshift.org/ocp-arm64/release-5-arm64:5.0.0-0.nightly-arm64-2026-08-18-145649

@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 66d09281-1012-4fa6-aca3-9976af46cee5

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

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

@eslutsky eslutsky changed the title Rebase release 5.0 5.0.0 0.nightly 2026 08 18 203845 amd64 2026 08 18 arm64 2026 08 18 rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64 Aug 20, 2026
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2026
@eslutsky

Copy link
Copy Markdown
Contributor Author

/retest

@copejon

copejon commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

/test e2e-aws-tests-bootc-el10

@copejon

copejon commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

/test verify

@eslutsky

Copy link
Copy Markdown
Contributor Author

the tests failing on upgrade , hitting the ovn-k bug when starting Microshift on 4.21 example: `
el96-yminus2@el98-src@upgrade-ok

@pacevedom pacevedom left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2026
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, pacevedom

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

@eslutsky

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests
/override ci/prow/e2e-aws-tests-arm
/override ci/prow/e2e-aws-tests-bootc-arm-el9
/override ci/prow/e2e-aws-tests-bootc-arm-el10
/override ci/prow/e2e-aws-tests-bootc-el9
/override ci/prow/e2e-aws-tests-bootc-el10

@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

@eslutsky: Overrode contexts on behalf of eslutsky: ci/prow/e2e-aws-tests, ci/prow/e2e-aws-tests-arm, ci/prow/e2e-aws-tests-bootc-arm-el10, ci/prow/e2e-aws-tests-bootc-arm-el9, ci/prow/e2e-aws-tests-bootc-el10, ci/prow/e2e-aws-tests-bootc-el9

Details

In response to this:

/override ci/prow/e2e-aws-tests
/override ci/prow/e2e-aws-tests-arm
/override ci/prow/e2e-aws-tests-bootc-arm-el9
/override ci/prow/e2e-aws-tests-bootc-arm-el10
/override ci/prow/e2e-aws-tests-bootc-el9
/override ci/prow/e2e-aws-tests-bootc-el10

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.

@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

@eslutsky: 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 57030ee link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc-arm-el9 57030ee link true /test e2e-aws-tests-bootc-arm-el9
ci/prow/e2e-aws-tests-bootc-el9 57030ee link true /test e2e-aws-tests-bootc-el9
ci/prow/e2e-aws-tests-bootc-el10 57030ee link true /test e2e-aws-tests-bootc-el10
ci/prow/e2e-aws-tests-bootc-arm-el10 57030ee link true /test e2e-aws-tests-bootc-arm-el10
ci/prow/e2e-aws-tests-arm 57030ee link true /test e2e-aws-tests-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.

@pacevedom pacevedom changed the title rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64 NO-ISSUE: rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64 Aug 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@eslutsky: This pull request explicitly references no jira issue.

Details

In response to this:

running rebase manually:

./scripts/auto-rebase/rebase.sh to registry.ci.openshift.org/ocp/release-5:5.0.0-0.nightly-2026-08-18-203845 registry.ci.openshift.org/ocp-arm64/release-5-arm64:5.0.0-0.nightly-arm64-2026-08-18-145649

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 Aug 21, 2026
@pacevedom

Copy link
Copy Markdown
Contributor

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 21, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

/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.

@pacevedom

Copy link
Copy Markdown
Contributor

/label jira/valid-bug
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Aug 21, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 00a7f8e into openshift:release-5.0 Aug 21, 2026
18 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.

4 participants