Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2026-04-01-194622_amd64-2026-04-01_arm64-2026-04-02#6448

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2026-04-01-194622_amd64-2026-04-01_arm64-2026-04-02
Apr 2, 2026
Merged

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2026-04-01-194622_amd64-2026-04-01_arm64-2026-04-02#6448
openshift-merge-bot[bot] merged 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2026-04-01-194622_amd64-2026-04-01_arm64-2026-04-02

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.19.0-0.nightly-2026-04-01-194622
arm64: 4.19.0-0.nightly-arm64-2026-04-02-032829
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/2039553735356583936

  • cluster-network-operator embedded-component b7adb6895b84c1916904e6eccd93ce578731171f to c56dbe730979a72781c87e01bb5bccffe527e6c6

    • e97a257 2026-01-21T09:06:18+00:00 Skip _stackmanager execution for libreswan 5.3+
  • machine-config-operator embedded-component 18f009eeb40748895fe8a6eba3778ad275655124 to 9c50d5330ae771d7e8682cbb58480867b2a874da

    • ebbe491b 2026-03-28T10:36:19+00:00 server: re-order logger setting
  • operator-framework-olm embedded-component 457b7eb2fdaeb469c117c3e87201ba88281795b4 to 93649380ab6fdccf8ec1716f89162b506c7de172

/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 Apr 2, 2026
@openshift-ci openshift-ci Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Apr 2, 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.19.0-0.nightly-2026-04-01-194622
arm64: 4.19.0-0.nightly-arm64-2026-04-02-032829
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/2039553735356583936

  • cluster-network-operator embedded-component b7adb6895b84c1916904e6eccd93ce578731171f to c56dbe730979a72781c87e01bb5bccffe527e6c6

  • e97a257 2026-01-21T09:06:18+00:00 Skip _stackmanager execution for libreswan 5.3+

  • machine-config-operator embedded-component 18f009eeb40748895fe8a6eba3778ad275655124 to 9c50d5330ae771d7e8682cbb58480867b2a874da

  • ebbe491b 2026-03-28T10:36:19+00:00 server: re-order logger setting

  • operator-framework-olm embedded-component 457b7eb2fdaeb469c117c3e87201ba88281795b4 to 93649380ab6fdccf8ec1716f89162b506c7de172

  • 70ea3b50 2026-03-30T14:20:21+08:00 Fix nil pointer dereference in sortUnpackJobs when sorting non-failed jobs ([release-4.17] USHIFT-3776: Remove skip of topolvm check for crel image #3793)

/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 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 Apr 2, 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 pacevedom and pmtk April 2, 2026 04:17
@eslutsky
Copy link
Copy Markdown
Contributor

eslutsky commented Apr 2, 2026

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 2, 2026

@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

eslutsky commented Apr 2, 2026

/lgtm
/verified by ci

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

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 2, 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

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

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
Copy Markdown
Contributor

openshift-ci Bot commented Apr 2, 2026

[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 Apr 2, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit d771ddd into release-4.19 Apr 2, 2026
13 checks passed
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.19-4.19.0-0.nightly-2026-04-01-194622_amd64-2026-04-01_arm64-2026-04-02 branch April 2, 2026 12:06
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