Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2025-03-19-173101_amd64-2025-03-19_arm64-2025-03-19#4707

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

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

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.17.0-0.nightly-2025-03-19-173101
arm64: 4.17.0-0.nightly-arm64-2025-03-19-231421
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1902571155663884288

  • machine-config-operator embedded-component a2af041b7eb58071d034090e0b451b51177a147f to e22d6adfdffb9ee3af2b5518910c22e231306a25
    • e472fcdc 2025-03-18T00:12:57+00:00 daemon: ensure ostree-finalize-staged is started before rebooting
    • 4d44c277 2025-02-28T01:18:04+00:00 Enforce VIPs to be collocated at the same host

/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 20, 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-19-173101
arm64: 4.17.0-0.nightly-arm64-2025-03-19-231421
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1902571155663884288

  • machine-config-operator embedded-component a2af041b7eb58071d034090e0b451b51177a147f to e22d6adfdffb9ee3af2b5518910c22e231306a25
  • e472fcdc 2025-03-18T00:12:57+00:00 daemon: ensure ostree-finalize-staged is started before rebooting
  • 4d44c277 2025-02-28T01:18:04+00:00 Enforce VIPs to be collocated at the same host

/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 20, 2025
@openshift-ci openshift-ci bot requested review from copejon and pliurh March 20, 2025 04:17
@copejon
Copy link
Contributor

copejon commented Mar 20, 2025

A broad network issue resulted in numerous job failures. It's since been fix, so retrying once

/retest

@copejon copejon self-assigned this Mar 20, 2025
@openshift-ci
Copy link
Contributor

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

@copejon
Copy link
Contributor

copejon commented Mar 20, 2025

/lgtm

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

openshift-ci bot commented Mar 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, 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 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7d6d11b into release-4.17 Mar 20, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.17-4.17.0-0.nightly-2025-03-19-173101_amd64-2025-03-19_arm64-2025-03-19 branch March 20, 2025 21:51
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