Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-09-19-111328_amd64-2025-09-19_arm64-2025-09-19#5502

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-09-19-111328_amd64-2025-09-19_arm64-2025-09-19
Sep 22, 2025
Merged

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-09-19-111328_amd64-2025-09-19_arm64-2025-09-19#5502
openshift-merge-bot[bot] merged 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-09-19-111328_amd64-2025-09-19_arm64-2025-09-19

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-09-19-111328
arm64: 4.19.0-0.nightly-arm64-2025-09-19-232733
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1969975332136030208

  • machine-config-operator embedded-component 37499cebe4e30aea812eb2a0e0cb5ed9ee961c5f to 9c2ef56a15a271c5e2332d648f012f867bd1c147
    • 157956c5 2025-09-16T20:33:23+00:00 OCPBUGS-61695: Override NMState service definition

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

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 22, 2025
@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.19.0-0.nightly-2025-09-19-111328
arm64: 4.19.0-0.nightly-arm64-2025-09-19-232733
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1969975332136030208

  • machine-config-operator embedded-component 37499cebe4e30aea812eb2a0e0cb5ed9ee961c5f to 9c2ef56a15a271c5e2332d648f012f867bd1c147
  • 157956c5 2025-09-16T20:33:23+00:00 OCPBUGS-61695: Override NMState service definition

/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 Sep 22, 2025
@openshift-ci-robot
Copy link

@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 eslutsky and jogeo September 22, 2025 04:22
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

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

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm

@pacevedom
Copy link
Contributor

/verified by CI

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 22, 2025
@openshift-ci-robot
Copy link

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: microshift-rebase-script[bot], 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 22, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit d3ed0a0 into release-4.19 Sep 22, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.19-4.19.0-0.nightly-2025-09-19-111328_amd64-2025-09-19_arm64-2025-09-19 branch September 22, 2025 07:20
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