NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2025-01-22-112731_amd64-2025-01-22_arm64-2025-01-22

[microshift-rebase-script]

amd64: 4.15.0-0.nightly-2025-01-22-112731
arm64: 4.15.0-0.nightly-arm64-2025-01-22-202431
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1882277409722470400

• operator-framework-olm embedded-component f690dd8788b7334ff6d593a2d2f9db077db73d08 to b500cb365122dd2c1c0234c5227723bb9d36c2f1
  • df32b3ef 2025-01-20T11:24:58+01:00 bump golang.org/x/net to 0.34.0 (NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-06-13-084629_amd64-2024-06-13_arm64-2024-06-13 #3485)
  • 1076c3b6 2025-01-20T11:24:27+01:00 Upgrade github.com/joelanford/ignore from v0.1.0 to v0.1.1 (USHIFT-898: Port the Getting Started procedure to use RHEL 9 and MicroShift 4.13 packages #1527)
  • ae0feaca 2025-01-20T11:23:54+01:00 bump golang.org/x/net to 0.34.0 (build(deps): bump actions/download-artifact from 1 to 2.0.10 #387)

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

[openshift-ci-robot]

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

Details

In response to this:

amd64: 4.15.0-0.nightly-2025-01-22-112731
arm64: 4.15.0-0.nightly-arm64-2025-01-22-202431
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1882277409722470400

• operator-framework-olm embedded-component f690dd8788b7334ff6d593a2d2f9db077db73d08 to b500cb365122dd2c1c0234c5227723bb9d36c2f1
• df32b3ef 2025-01-20T11:24:58+01:00 bump golang.org/x/net to 0.34.0 (NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-06-13-084629_amd64-2024-06-13_arm64-2024-06-13 #3485)
• 1076c3b6 2025-01-20T11:24:27+01:00 Upgrade github.com/joelanford/ignore from v0.1.0 to v0.1.1 (USHIFT-898: Port the Getting Started procedure to use RHEL 9 and MicroShift 4.13 packages #1527)
• ae0feaca 2025-01-20T11:23:54+01:00 bump golang.org/x/net to 0.34.0 (build(deps): bump actions/download-artifact from 1 to 2.0.10 #387)

/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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign jerpeter1 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pmtk]

/retest

[openshift-ci]

@microshift-rebase-script[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/microshift-metal-tests-arm	d5268d7	link	true	/test microshift-metal-tests-arm

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.

[pacevedom]

/close

[openshift-ci]

@pacevedom: Closed this PR.

Details

In response to this:

/close

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.

[openshift-merge-robot]

PR needs rebase.

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.