Skip to content

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.18.0-0.nightly-2025-02-03-072713
arm64: 4.18.0-0.nightly-arm64-2025-02-04-012511
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-rebase-on-nightlies/1886625934937690112

  • cluster-network-operator embedded-component 4616940d5e04f53b5bed811449b89acf2bb11514 to 224efe3703ae1b01eeb815d9db6dd5ccc445feff

    • 2add839 2025-01-30T17:47:23+00:00 OVNK should be able to annotate network ID on NADs
  • ovn-kubernetes image-amd64 9f68300ef68a4c77a61007208eb6bcbca50a9015 to 5086614cde9fbec2cce4c8184ea407adaef5c2a3

    • 2a8db097 2025-02-01T16:28:46+00:00 Fixes 1 minute delay for primary UDN controllers to start
    • 97e762bc 2025-02-01T16:28:46+00:00 Fix UDN and CUDN subnet validation

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

@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.18.0-0.nightly-2025-02-03-072713
arm64: 4.18.0-0.nightly-arm64-2025-02-04-012511
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-rebase-on-nightlies/1886625934937690112

  • cluster-network-operator embedded-component 4616940d5e04f53b5bed811449b89acf2bb11514 to 224efe3703ae1b01eeb815d9db6dd5ccc445feff

  • 2add839 2025-01-30T17:47:23+00:00 OVNK should be able to annotate network ID on NADs

  • ovn-kubernetes image-amd64 9f68300ef68a4c77a61007208eb6bcbca50a9015 to 5086614cde9fbec2cce4c8184ea407adaef5c2a3

  • 2a8db097 2025-02-01T16:28:46+00:00 Fixes 1 minute delay for primary UDN controllers to start

  • 97e762bc 2025-02-01T16:28:46+00:00 Fix UDN and CUDN subnet validation

/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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 4, 2025
@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 Feb 4, 2025
@openshift-ci openshift-ci bot requested review from agullon and ggiguash February 4, 2025 04:27
Copy link
Contributor

openshift-ci bot commented Feb 4, 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.

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

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

openshift-ci bot commented Feb 4, 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

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 Feb 4, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit d8bc093 into release-4.18 Feb 4, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.18-4.18.0-0.nightly-2025-02-03-072713_amd64-2025-02-03_arm64-2025-02-04 branch February 4, 2025 07:32
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