Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-10-22-141259_amd64-2025-10-22_arm64-2025-10-22#5666

Closed
microshift-rebase-script[bot] wants to merge 1 commit intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-10-22-141259_amd64-2025-10-22_arm64-2025-10-22
Closed

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-10-22-141259_amd64-2025-10-22_arm64-2025-10-22#5666
microshift-rebase-script[bot] wants to merge 1 commit intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-10-22-141259_amd64-2025-10-22_arm64-2025-10-22

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-10-22-141259
arm64: 4.19.0-0.nightly-arm64-2025-10-22-130329
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1982658672236433408

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

@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.19.0-0.nightly-2025-10-22-141259
arm64: 4.19.0-0.nightly-arm64-2025-10-22-130329
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1982658672236433408

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

@microshift-rebase-script
Copy link
Contributor Author

Extra messages:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 27, 2025
@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. labels Oct 27, 2025
@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

Extra messages:

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 27, 2025
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

Extra messages:

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 requested review from jerpeter1 and pacevedom October 27, 2025 04:32
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 27, 2025

[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 ggiguash 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

@eslutsky
Copy link
Contributor

/test verify

@eslutsky
Copy link
Contributor

eslutsky commented Oct 27, 2025

looks like infra error

error: unable to parse image registry.redhat.io/rhoai/odh-rhel9-operator@sha256:9292ff588ed93a002187b070b644c16de2696c0490c1c2c4d29a56e217963436: cannot retrieve image configuration for manifest sha256:dccc7c6cf920da7ffeadbad42f5727f2d58d54ceef399ac98441345d06ff10c4 in manifest list sha256:9292ff588ed93a002187b070b644c16de2696c0490c1c2c4d29a56e217963436: received unexpected HTTP status: 502 Bad Gateway

@eslutsky
Copy link
Contributor

/test verify

2 similar comments
@eslutsky
Copy link
Contributor

/test verify

@eslutsky
Copy link
Contributor

/test verify

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 29, 2025

@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/verify d5aa451 link true /test verify

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

/close

@openshift-ci openshift-ci bot closed this Oct 30, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 30, 2025

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

@microshift-rebase-script microshift-rebase-script bot deleted the rebase-release-4.19-4.19.0-0.nightly-2025-10-22-141259_amd64-2025-10-22_arm64-2025-10-22 branch October 31, 2025 04:25
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.

3 participants