NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2026-09-13-232117_amd64-2026-09-13_arm64-2026-07-14 - #7370
Conversation
|
/pipeline auto |
|
@microshift-rebase-script[bot]: This pull request explicitly references no jira issue. DetailsIn 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. |
|
/verified by automatic-rebase |
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo. DetailsIn 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. |
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Pipeline controller notification The |
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Scheduling tests matching the |
1 similar comment
|
Scheduling tests matching the |
|
/pipeline required |
|
Scheduling tests matching the |
|
/pipeline auto |
|
Pipeline controller notification The |
|
/test e2e-aws-tests |
|
@microshift-rebase-script[bot]: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
amd64: 4.20.0-0.nightly-2026-09-13-232117
arm64: 4.20.0-0.nightly-arm64-2026-07-14-154502
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/2099347760485502976
cluster-ingress-operator embedded-component f86aaea4136dfea16e62290bd50ecdd1a8b22b3f to 8e4c40f161d8341d640659ca2779a4294960c183
machine-config-operator embedded-component 9bc526090b3b087f1d9eaaea86901a3f95c2c997 to d87a335c2ca5c48ca5aa485754d3548f5ecb42af
operator-framework-olm embedded-component 1628e53777871f6c264d41a870cc4ee7248106f2 to e1d090d165aa3e31de614b18da7cf4dd2f6976f6
/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug