Skip to content

NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2025-02-07-235831_amd64-2025-02-08_arm64-2025-02-09 #4526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.18.0-0.nightly-2025-02-07-235831
arm64: 4.18.0-0.nightly-arm64-2025-02-09-091710
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-rebase-on-nightlies/1888800442146623488

  • cluster-network-operator embedded-component e98cac9c69c0cdf0a08c3a6f688c11dae2ac7d93 to b48488a6ee4c9e1ae778217817266baddd5f3e51

    • 1fcce67 2025-01-29T07:22:33+00:00 Update egressfirewall CRD to be consistent with ovn-kubernetes repo
  • machine-config-operator embedded-component d6090f11285d3b9a9262290f17bc3f90eb3dd8e5 to 120ba674540c81513d1a701b99c8d424dbb41887

    • 50cbe275 2025-01-28T15:57:29+00:00 OCPBUGS-46072: create /run/nodeip-configuration before use
    • 36e34c5d 2024-12-12T10:48:17+00:00 Update the storage.conf configuration file template

/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 Feb 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.18.0-0.nightly-2025-02-07-235831
arm64: 4.18.0-0.nightly-arm64-2025-02-09-091710
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-rebase-on-nightlies/1888800442146623488

  • cluster-network-operator embedded-component e98cac9c69c0cdf0a08c3a6f688c11dae2ac7d93 to b48488a6ee4c9e1ae778217817266baddd5f3e51

  • 1fcce67 2025-01-29T07:22:33+00:00 Update egressfirewall CRD to be consistent with ovn-kubernetes repo

  • machine-config-operator embedded-component d6090f11285d3b9a9262290f17bc3f90eb3dd8e5 to 120ba674540c81513d1a701b99c8d424dbb41887

  • 50cbe275 2025-01-28T15:57:29+00:00 OCPBUGS-46072: create /run/nodeip-configuration before use

  • 36e34c5d 2024-12-12T10:48:17+00:00 Update the storage.conf configuration file template

/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 Feb 10, 2025
@openshift-ci openshift-ci bot requested review from agullon and ggiguash February 10, 2025 04:28
Copy link
Contributor

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

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 10, 2025
Copy link
Contributor

openshift-ci bot commented Feb 10, 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 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit cf04713 into release-4.18 Feb 10, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.18-4.18.0-0.nightly-2025-02-07-235831_amd64-2025-02-08_arm64-2025-02-09 branch February 10, 2025 08:02
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