Skip to content

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-03-20-220245
arm64: 4.19.0-0.nightly-arm64-2025-03-20-200021
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1902933478949785600

  • api embedded-component 8a7efbfb531684ef0ff566a882096df03e0f499c to 477760860ebdd921db389cf539439b0ec1064179

    • 28ccba1d 2025-03-19T16:40:27-04:00 remove inactive reviewers and ex-Red Hatters from OWNERS, add everettraven
    • 80f8dcff 2025-03-19T11:12:08+00:00 Remove patch tags from CRD conditions
    • ea7057f8 2025-03-18T14:11:59+00:00 Update KAL to the latest version
    • c86f460c 2025-03-11T10:46:36+01:00 add MaxAllowedBlockVolumesPerNode field to VSphereCSIDriverConfigSpec
  • cluster-network-operator embedded-component 510b7508ad7a66d1742c5d9f83a4143fa860029c to 1daca87a5c6ebd5e6d7b5bcc4374119b59061af6

    • 11c08e6 2025-03-17T23:22:49+01:00 Check on ipsec.service instead of libreswan package on host
    • cb99bc3 2025-03-17T20:02:27+01:00 Add version check for machine config operator
    • 865ac69 2025-03-17T19:38:45+01:00 Mount top level directory for IPsec host paths
    • 37693e9 2025-03-17T19:38:45+01:00 Move to use newer IPsec DaemonSets irrespective of MCP state

/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.19.0-0.nightly-2025-03-20-220245
arm64: 4.19.0-0.nightly-arm64-2025-03-20-200021
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1902933478949785600

  • api embedded-component 8a7efbfb531684ef0ff566a882096df03e0f499c to 477760860ebdd921db389cf539439b0ec1064179

  • 28ccba1d 2025-03-19T16:40:27-04:00 remove inactive reviewers and ex-Red Hatters from OWNERS, add everettraven

  • 80f8dcff 2025-03-19T11:12:08+00:00 Remove patch tags from CRD conditions

  • ea7057f8 2025-03-18T14:11:59+00:00 Update KAL to the latest version

  • c86f460c 2025-03-11T10:46:36+01:00 add MaxAllowedBlockVolumesPerNode field to VSphereCSIDriverConfigSpec

  • cluster-network-operator embedded-component 510b7508ad7a66d1742c5d9f83a4143fa860029c to 1daca87a5c6ebd5e6d7b5bcc4374119b59061af6

  • 11c08e6 2025-03-17T23:22:49+01:00 Check on ipsec.service instead of libreswan package on host

  • cb99bc3 2025-03-17T20:02:27+01:00 Add version check for machine config operator

  • 865ac69 2025-03-17T19:38:45+01:00 Mount top level directory for IPsec host paths

  • 37693e9 2025-03-17T19:38:45+01:00 Move to use newer IPsec DaemonSets irrespective of MCP state

/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 Mar 21, 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 Mar 21, 2025
@openshift-ci openshift-ci bot requested review from dhensel-rh and eslutsky March 21, 2025 04:21
Copy link
Contributor

openshift-ci bot commented Mar 21, 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.

@ggiguash
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Mar 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Mar 21, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit e3a057a into main Mar 21, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.19.0-0.nightly-2025-03-20-220245_amd64-2025-03-20_arm64-2025-03-20 branch March 21, 2025 05:55
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