Skip to content

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-05-25-200009_amd64-2026-05-25_arm64-2026-05-26#6733

Open
microshift-rebase-script[bot] wants to merge 4 commits into
release-4.22from
rebase-release-4.22-4.22.0-0.nightly-2026-05-25-200009_amd64-2026-05-25_arm64-2026-05-26
Open

NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-05-25-200009_amd64-2026-05-25_arm64-2026-05-26#6733
microshift-rebase-script[bot] wants to merge 4 commits into
release-4.22from
rebase-release-4.22-4.22.0-0.nightly-2026-05-25-200009_amd64-2026-05-25_arm64-2026-05-26

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.22.0-0.nightly-2026-05-25-200009
arm64: 4.22.0-0.nightly-arm64-2026-05-26-031550
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2059122602625994752

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.22.0-0.nightly-2026-05-25-200009
arm64: 4.22.0-0.nightly-arm64-2026-05-26-031550
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.22-periodics-rebase-on-nightlies/2059122602625994752

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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 May 26, 2026
@openshift-ci openshift-ci Bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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 May 26, 2026
@openshift-ci openshift-ci Bot requested review from copejon and pmtk May 26, 2026 04:19
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign ggiguash for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD f7ae765 and 2 for PR HEAD e0ee560 in total

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test ocp-full-conformance-serial-rhel-eus
/test test-unit

Added by prow-jobs-for-pull-requests.sh 🤖

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@microshift-rebase-script[bot]: 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/test-unit e0ee560 link true /test test-unit
ci/prow/ocp-full-conformance-serial-rhel-eus e0ee560 link true /test ocp-full-conformance-serial-rhel-eus

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant