Skip to content

NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2026-03-25-052622_amd64-2026-03-25_arm64-2026-03-26#6406

Merged
openshift-merge-bot[bot] merged 5 commits into
release-4.18from
rebase-release-4.18-4.18.0-0.nightly-2026-03-25-052622_amd64-2026-03-25_arm64-2026-03-26
Mar 26, 2026
Merged

NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2026-03-25-052622_amd64-2026-03-25_arm64-2026-03-26#6406
openshift-merge-bot[bot] merged 5 commits into
release-4.18from
rebase-release-4.18-4.18.0-0.nightly-2026-03-25-052622_amd64-2026-03-25_arm64-2026-03-26

Conversation

@microshift-rebase-script

Copy link
Copy Markdown
Contributor

amd64: 4.18.0-0.nightly-2026-03-25-052622
arm64: 4.18.0-0.nightly-arm64-2026-03-26-022314
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/2037017074370351104

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

@microshift-rebase-script

Copy link
Copy Markdown
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 26, 2026
@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.18.0-0.nightly-2026-03-25-052622
arm64: 4.18.0-0.nightly-arm64-2026-03-26-022314
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/2037017074370351104

/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 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 Mar 26, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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 March 26, 2026 04:15
@openshift-ci

openshift-ci Bot commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

@microshift-rebase-script[bot]: all tests passed!

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.

@eslutsky

Copy link
Copy Markdown
Contributor

/lgtm
/verified by CI

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

Copy link
Copy Markdown

@eslutsky: 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 Mar 26, 2026
@openshift-ci

openshift-ci Bot commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, microshift-rebase-script[bot]

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 Mar 26, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 6dbff52 into release-4.18 Mar 26, 2026
14 checks passed
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.18-4.18.0-0.nightly-2026-03-25-052622_amd64-2026-03-25_arm64-2026-03-26 branch March 26, 2026 07:31
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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants