-
Notifications
You must be signed in to change notification settings - Fork 216
NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-03-18-071705_amd64-2025-03-18_arm64-2025-03-18 #4701
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]: This pull request explicitly references no jira issue. In response to this:
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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: microshift-rebase-script[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@microshift-rebase-script[bot]: The following tests failed, say
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. |
Bootc upgrade tests failed. Appears to be a bug in the bootc image build:
|
Determined that this is a bug in the base bootc images. The cause has been identified upstream. Closing this PR as it likely won't be merged before the next iteration of rebase jobs. /close |
/close |
@copejon: Closed this PR. In response to this:
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. |
@copejon: Closed this PR. In response to this:
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. |
amd64: 4.19.0-0.nightly-2025-03-18-071705
arm64: 4.19.0-0.nightly-arm64-2025-03-18-210236
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1902208752895922176
cluster-ingress-operator embedded-component 7dc12cf28557f8c80460435649cfc393761e0285 to 924279a66d42d633d658113846d68e8d3805ec26
cluster-kube-apiserver-operator embedded-component c13665bdedd2ee30d28ff83c187ea739d9b8094d to e41854880dcb1a9df3322c1494c93e9a9ac0babe
cluster-network-operator embedded-component b2f717758e01faa85ece045aaa63f65dbbce7d17 to 510b7508ad7a66d1742c5d9f83a4143fa860029c
etcd embedded-component bd0cae2096abb1d2087e858bbce3f9c06b215f8d to 80d288f7ccb6c11128e2d697e7d26805c487150b
kubernetes embedded-component d6f2dd28529e5ecc8cdffaf443253f74382c2b60 to 2ed17b46fa89c438d5983268bdc352ba8bd9b4bb
machine-config-operator embedded-component adafd58169f40eec1110a9fd47473457ca8e5f9d to 13ad337e5ae9399c305269daaa22e09a610d61a6
operator-framework-olm embedded-component 6dd1017cdc814695820aeeb95be6cc28d6c411b5 to e7c4a6900a8b47fef5bf8f5587b0088ba4a057c8
dnf repository-packages
#3536)kubernetes image-amd64 d6f2dd28529e5ecc8cdffaf443253f74382c2b60 to 2ed17b46fa89c438d5983268bdc352ba8bd9b4bb
kubernetes image-arm64 f4a27c46e464f735615c60fc0b067471e7073e13 to 2ed17b46fa89c438d5983268bdc352ba8bd9b4bb
The change list was truncated. See scripts/auto-rebase/changelog.txt in the PR for the full details.
/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug