Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-09-06-192226_amd64-2025-09-06_arm64-2025-09-06#5420

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-09-06-192226_amd64-2025-09-06_arm64-2025-09-06
Sep 8, 2025
Merged

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-09-06-192226_amd64-2025-09-06_arm64-2025-09-06#5420
openshift-merge-bot[bot] merged 5 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-09-06-192226_amd64-2025-09-06_arm64-2025-09-06

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-09-06-192226
arm64: 4.19.0-0.nightly-arm64-2025-09-06-192217
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1964901788037419008

  • api embedded-component c9f500dc7ca317fcb4028b172a8c638305976e7f to 5b2b8cafdd825e60f37a3ce6f8dac0ad1732293e

    • d37c9b38 2025-09-03T13:07:09-04:00 features: Lift feature gate for PIS in 4.19
    • 75435dd9 2025-06-20T08:37:27-04:00 promote MachineConfigNode feature gate to default
  • cluster-network-operator embedded-component bc27b42976486bd395fdbb0f4fbc9a5a8499be2c to bb6470c3cfbb1ecdaf78acac340e6a307bcd5231

    • 5ef1741 2025-09-03T11:03:54+02:00 Ran make update-codegen
    • e24845b 2025-09-03T10:48:21+02:00 Bump openshift/api to commit where RA was GA-ed
  • machine-config-operator embedded-component 1cc3b020cb2d5cdcb9135de39ddbd0ddd494495f to 1a3a559a1c78f664e9812812c14e1b02687a96bc

    • 5e0c91f2 2025-08-04T20:59:17+00:00 OCPBUGS-55971: Enable debug logging for nodeip-configuration

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug
/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-06-192226
arm64: 4.19.0-0.nightly-arm64-2025-09-06-192217
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1964901788037419008

  • api embedded-component c9f500dc7ca317fcb4028b172a8c638305976e7f to 5b2b8cafdd825e60f37a3ce6f8dac0ad1732293e

  • d37c9b38 2025-09-03T13:07:09-04:00 features: Lift feature gate for PIS in 4.19

  • 75435dd9 2025-06-20T08:37:27-04:00 promote MachineConfigNode feature gate to default

  • cluster-network-operator embedded-component bc27b42976486bd395fdbb0f4fbc9a5a8499be2c to bb6470c3cfbb1ecdaf78acac340e6a307bcd5231

  • 5ef1741 2025-09-03T11:03:54+02:00 Ran make update-codegen

  • e24845b 2025-09-03T10:48:21+02:00 Bump openshift/api to commit where RA was GA-ed

  • machine-config-operator embedded-component 1cc3b020cb2d5cdcb9135de39ddbd0ddd494495f to 1a3a559a1c78f664e9812812c14e1b02687a96bc

  • 5e0c91f2 2025-08-04T20:59:17+00:00 OCPBUGS-55971: Enable debug logging for nodeip-configuration

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug
/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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 8, 2025
@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 8, 2025
@pacevedom
Copy link
Contributor

/test images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 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.

@pacevedom
Copy link
Contributor

/verified by automatic-rebase

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 8, 2025
@openshift-ci-robot
Copy link

@pacevedom: This PR has been marked as verified by automatic-rebase.

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.

@pacevedom
Copy link
Contributor

/verified cancel

@openshift-ci-robot
Copy link

@pacevedom: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified cancel

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
Contributor

/verified remove

@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Sep 8, 2025
@openshift-ci-robot
Copy link

@pacevedom: The verified label has been removed.

Details

In response to this:

/verified remove

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.

@copejon
Copy link
Contributor

copejon commented Sep 8, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, 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 Sep 8, 2025
@copejon
Copy link
Contributor

copejon commented Sep 8, 2025

/label verified

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2025

@copejon: The label(s) /label verified cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label verified

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.

@copejon
Copy link
Contributor

copejon commented Sep 8, 2025

/verified

@openshift-ci-robot
Copy link

@copejon: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified

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.

@copejon
Copy link
Contributor

copejon commented Sep 8, 2025

/label verified

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2025

@copejon: The label(s) /label verified cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label verified

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.

@pacevedom
Copy link
Contributor

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 8, 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-merge-bot openshift-merge-bot bot merged commit 5c535f5 into release-4.19 Sep 8, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.19-4.19.0-0.nightly-2025-09-06-192226_amd64-2025-09-06_arm64-2025-09-06 branch September 8, 2025 22: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.

3 participants