Skip to content

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Jan 30, 2026

Swap layer numbers so release is layer 4 and upstream is layer 5. This aligns bootc with non-bootc structure, facilitating easier backporting to release branches since the upstream layer only exists on main.

Swap layer numbers so release is layer 4 and upstream is layer 5.
This aligns bootc with non-bootc structure, facilitating easier
backporting to release branches since the upstream layer only
exists on main.

USHIFT-6544

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 30, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 30, 2026

@agullon: This pull request references USHIFT-6544 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Swap layer numbers so release is layer 4 and upstream is layer 5. This aligns bootc with non-bootc structure, facilitating easier backporting to release branches since the upstream layer only exists on main.

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 a review from jerpeter1 January 30, 2026 12:48
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon

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

The pull request process is described 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-ci openshift-ci bot requested a review from pmtk January 30, 2026 12:48
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 30, 2026
@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

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

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

2 similar comments
@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

@agullon
Copy link
Contributor Author

agullon commented Jan 30, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

@agullon: 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/e2e-aws-tests-bootc-release ebe0206 link true /test e2e-aws-tests-bootc-release

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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants