Skip to content

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-04-08-163320
arm64: 4.19.0-0.nightly-arm64-2025-04-09-202829
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1910181316020670464

  • ovn-kubernetes image-arm64 253890a6dead8e3ac594b9584334c163a2c768ac to e356c93468c4b686eca25a1ec92e7cf9ec0d8bf3

    • 27033e32 2025-04-07T15:24:32+02:00 EIP no reroute: allow multiple entries for pod to pod and pod to join
    • f76582f4 2025-04-03T20:00:36+02:00 ci: fix actions/setup-go@v5 warnings
    • 837a638b 2025-04-03T20:00:36+02:00 ci: fix submit code coverage to Coveralls
    • a3d569aa 2025-04-03T20:00:36+02:00 kind: rely on --force when removing containers and networks
    • cca01b1a 2025-04-03T10:35:42+02:00 Explicitly probe for frr-k8s webhook readiness
    • 764685a5 2025-03-19T18:09:35+08:00 unpin libreswan version
  • kubernetes image-arm64 c17291b1e40554b4e5b3ccff01b6d590af2e7a43 to e15f4f8936ca26f9de398b849c4632a57bba1914

    • 07d437ae1 2025-04-04T11:45:51+01:00 UPSTREAM: 130450: Fix implementation of ContainsCIDR to allow non-equal addresses

/label tide/merge-method-squash
/label cherry-pick-approved
/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 Apr 10, 2025
@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.19.0-0.nightly-2025-04-08-163320
arm64: 4.19.0-0.nightly-arm64-2025-04-09-202829
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1910181316020670464

  • ovn-kubernetes image-arm64 253890a6dead8e3ac594b9584334c163a2c768ac to e356c93468c4b686eca25a1ec92e7cf9ec0d8bf3

  • 27033e32 2025-04-07T15:24:32+02:00 EIP no reroute: allow multiple entries for pod to pod and pod to join

  • f76582f4 2025-04-03T20:00:36+02:00 ci: fix actions/setup-go@v5 warnings

  • 837a638b 2025-04-03T20:00:36+02:00 ci: fix submit code coverage to Coveralls

  • a3d569aa 2025-04-03T20:00:36+02:00 kind: rely on --force when removing containers and networks

  • cca01b1a 2025-04-03T10:35:42+02:00 Explicitly probe for frr-k8s webhook readiness

  • 764685a5 2025-03-19T18:09:35+08:00 unpin libreswan version

  • kubernetes image-arm64 c17291b1e40554b4e5b3ccff01b6d590af2e7a43 to e15f4f8936ca26f9de398b849c4632a57bba1914

  • 07d437ae1 2025-04-04T11:45:51+01:00 UPSTREAM: 130450: Fix implementation of ContainsCIDR to allow non-equal addresses

/label tide/merge-method-squash
/label cherry-pick-approved
/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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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 10, 2025
@openshift-ci openshift-ci bot requested review from pacevedom and vanhalenar April 10, 2025 04:11
Copy link
Contributor

openshift-ci bot commented Apr 10, 2025

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

Full PR test history. Your PR dashboard.

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.

@pmtk
Copy link
Member

pmtk commented Apr 10, 2025

/lgtm

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

openshift-ci bot commented Apr 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 533bb19 into main Apr 10, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.19.0-0.nightly-2025-04-08-163320_amd64-2025-04-08_arm64-2025-04-09 branch April 10, 2025 07:38
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants