Skip to content

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-05-04-160406_amd64-2026-05-04_arm64-2026-05-04#6623

Closed
microshift-rebase-script[bot] wants to merge 7 commits intomainfrom
rebase-release-5.0-5.0.0-0.nightly-2026-05-04-160406_amd64-2026-05-04_arm64-2026-05-04
Closed

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-05-04-160406_amd64-2026-05-04_arm64-2026-05-04#6623
microshift-rebase-script[bot] wants to merge 7 commits intomainfrom
rebase-release-5.0-5.0.0-0.nightly-2026-05-04-160406_amd64-2026-05-04_arm64-2026-05-04

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 5.0.0-0.nightly-2026-05-04-160406
arm64: 5.0.0-0.nightly-arm64-2026-05-04-233705
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-5.0-periodics-rebase-on-nightlies/2051512492609245184

/label tide/merge-method-squash
/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 May 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

amd64: 5.0.0-0.nightly-2026-05-04-160406
arm64: 5.0.0-0.nightly-arm64-2026-05-04-233705
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-5.0-periodics-rebase-on-nightlies/2051512492609245184

/label tide/merge-method-squash
/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. 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 May 5, 2026
@openshift-ci openshift-ci Bot requested review from kasturinarra and vanhalenar May 5, 2026 04:18
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 5, 2026

[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 pmtk 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:

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

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9a9d010 and 2 for PR HEAD 53420fd in total

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-bootc-arm-el10
/test e2e-aws-tests-bootc-arm-el9
/test e2e-aws-tests-bootc-el10
/test e2e-aws-tests-bootc-el9
/test test-rebase

Added by prow-jobs-for-pull-requests.sh 🤖

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-bootc-arm-el10
/test e2e-aws-tests-bootc-arm-el9
/test e2e-aws-tests-bootc-el10
/test e2e-aws-tests-bootc-el9

Added by prow-jobs-for-pull-requests.sh 🤖

@copejon
Copy link
Copy Markdown
Contributor

copejon commented May 6, 2026

/test e2e-aws-tests-bootc-el10

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 6, 2026

@microshift-rebase-script[bot]: The following tests 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/e2e-aws-tests-bootc-el10 53420fd link true /test e2e-aws-tests-bootc-el10
ci/prow/e2e-aws-tests-bootc-arm-el9 53420fd link true /test e2e-aws-tests-bootc-arm-el9
ci/prow/e2e-aws-tests-bootc-el9 53420fd link true /test e2e-aws-tests-bootc-el9

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
Copy Markdown
Contributor

copejon commented May 6, 2026

Closing: cert-manager v1.19.4 rebase added operator.openshift.io_trustmanagers.yaml and customresourcedefinition_bundles.trust.cert-manager.io.yml to assets/optional/cert-manager/crd/kustomization.yaml but the actual CRD files were not included in the commit. MicroShift fails to apply the cert-manager kustomization on every boot, cert-manager is never deployed, and greenboot times out after 20 minutes. All optionals scenarios fail; non-optionals scenarios pass.

/close

@openshift-ci openshift-ci Bot closed this May 6, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 6, 2026

@copejon: Closed this PR.

Details

In response to this:

Closing: cert-manager v1.19.4 rebase added operator.openshift.io_trustmanagers.yaml and customresourcedefinition_bundles.trust.cert-manager.io.yml to assets/optional/cert-manager/crd/kustomization.yaml but the actual CRD files were not included in the commit. MicroShift fails to apply the cert-manager kustomization on every boot, cert-manager is never deployed, and greenboot times out after 20 minutes. All optionals scenarios fail; non-optionals scenarios pass.

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

@microshift-rebase-script microshift-rebase-script Bot deleted the rebase-release-5.0-5.0.0-0.nightly-2026-05-04-160406_amd64-2026-05-04_arm64-2026-05-04 branch May 6, 2026 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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