Skip to content

Conversation

ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Mar 20, 2025

Depends on successful merge of openshift/release#63022

@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

openshift-ci-robot commented Mar 20, 2025

@ggiguash: This pull request references USHIFT-5475 which is a valid 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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 20, 2025
Copy link
Contributor

openshift-ci bot commented Mar 20, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@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-ci-robot
Copy link

openshift-ci-robot commented Mar 20, 2025

@ggiguash: This pull request references USHIFT-5475 which is a valid jira issue.

In response to this:

Depends on successful merge of openshift/release#63022

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.

@ggiguash ggiguash marked this pull request as ready for review March 20, 2025 11:38
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 20, 2025
@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 March 20, 2025 11:38
@ggiguash
Copy link
Contributor Author

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

@copejon
Copy link
Contributor

copejon commented Mar 20, 2025

Seems it's still affected by the bugged label:

[31mERROR[0m Switching: Pulling: Preparing import: Fetching manifest: Target image does not have ostree.bootable label

@ggiguash
Copy link
Contributor Author

Seems it's still affected by the bugged label:

[31mERROR[0m Switching: Pulling: Preparing import: Fetching manifest: Target image does not have ostree.bootable label

Yeah, any test would be affected unrelated to the code changes.
The previous failed tests ran before we disabled the affected upgrade tests.

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

openshift-ci bot commented Mar 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

Copy link
Contributor

openshift-ci bot commented Mar 21, 2025

@ggiguash: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 69e2b8f into openshift:main Mar 21, 2025
10 checks passed
@ggiguash ggiguash deleted the multi-arch-brew-image branch March 21, 2025 06:14
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. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants