Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2025-03-05-204715_amd64-2025-03-05_arm64-2025-03-05#4641

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2025-03-05-204715_amd64-2025-03-05_arm64-2025-03-05
Mar 6, 2025
Merged

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2025-03-05-204715_amd64-2025-03-05_arm64-2025-03-05#4641
openshift-merge-bot[bot] merged 4 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2025-03-05-204715_amd64-2025-03-05_arm64-2025-03-05

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.17.0-0.nightly-2025-03-05-204715
arm64: 4.17.0-0.nightly-arm64-2025-03-05-192157
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1897497602417496064

  • machine-config-operator embedded-component 467061987c1e6b90d8f854c9b0eec82fd8bd2d1c to 3da4faa0a834ce663e561f423f29bc0e941b6af5

    • 834f736b 2025-03-03T14:54:16-06:00 OCPBUGS-41489: configure-ovs workaround for ovs-if-br-ex bug
    • 4cfd4a5b 2025-02-26T17:15:42+00:00 daemon: update log verbs
    • 1eb23200 2025-02-17T16:50:13+00:00 OCPBUGS-46072: create /run/nodeip-configuration before use
  • oc image-amd64 2510f852661f4ace4fb5ae83de643e74e66ca36b to 0000b3ef257d07f423dfdf9b6d274214d1b0c846

    • 8f84a405 2025-02-25T12:24:13-05:00 Bump go-jose for CVE-2025-27144
    • f74e5086 2025-01-28T11:02:42-05:00 Address golang.org/x/* CVEs
  • oc image-arm64 2510f852661f4ace4fb5ae83de643e74e66ca36b to 0000b3ef257d07f423dfdf9b6d274214d1b0c846

    • 8f84a405 2025-02-25T12:24:13-05:00 Bump go-jose for CVE-2025-27144
    • f74e5086 2025-01-28T11:02:42-05:00 Address golang.org/x/* CVEs

/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 Mar 6, 2025
@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.17.0-0.nightly-2025-03-05-204715
arm64: 4.17.0-0.nightly-arm64-2025-03-05-192157
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1897497602417496064

  • machine-config-operator embedded-component 467061987c1e6b90d8f854c9b0eec82fd8bd2d1c to 3da4faa0a834ce663e561f423f29bc0e941b6af5

  • 834f736b 2025-03-03T14:54:16-06:00 OCPBUGS-41489: configure-ovs workaround for ovs-if-br-ex bug

  • 4cfd4a5b 2025-02-26T17:15:42+00:00 daemon: update log verbs

  • 1eb23200 2025-02-17T16:50:13+00:00 OCPBUGS-46072: create /run/nodeip-configuration before use

  • oc image-amd64 2510f852661f4ace4fb5ae83de643e74e66ca36b to 0000b3ef257d07f423dfdf9b6d274214d1b0c846

  • 8f84a405 2025-02-25T12:24:13-05:00 Bump go-jose for CVE-2025-27144

  • f74e5086 2025-01-28T11:02:42-05:00 Address golang.org/x/* CVEs

  • oc image-arm64 2510f852661f4ace4fb5ae83de643e74e66ca36b to 0000b3ef257d07f423dfdf9b6d274214d1b0c846

  • 8f84a405 2025-02-25T12:24:13-05:00 Bump go-jose for CVE-2025-27144

  • f74e5086 2025-01-28T11:02:42-05:00 Address golang.org/x/* CVEs

/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 Mar 6, 2025
@openshift-ci openshift-ci bot requested review from pacevedom and pmtk March 6, 2025 04:28
@eslutsky
Copy link
Contributor

eslutsky commented Mar 6, 2025

/lgtm

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

openshift-ci bot commented Mar 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, 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 Mar 6, 2025
@openshift-ci
Copy link
Contributor

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

@openshift-merge-bot openshift-merge-bot bot merged commit d82d99b into release-4.17 Mar 6, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.17-4.17.0-0.nightly-2025-03-05-204715_amd64-2025-03-05_arm64-2025-03-05 branch March 6, 2025 11:44
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