Skip to content

[release-4.21] USHIFT-6362: Add iso deployment for rpmostree release scenarios#6056

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
kasturinarra:fix_iso_421
Jan 10, 2026
Merged

[release-4.21] USHIFT-6362: Add iso deployment for rpmostree release scenarios#6056
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.21from
kasturinarra:fix_iso_421

Conversation

@kasturinarra
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from agullon and copejon January 9, 2026 18:32
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2026
@kasturinarra kasturinarra changed the title Add iso deployment for rpmostree release scenarios [release-4.21] USHIFT-6362: Add iso deployment for rpmostree release scenarios Jan 9, 2026
@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 9, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 9, 2026

@kasturinarra: This pull request references USHIFT-6362 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.21.0" version, but no target version was set.

Details

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.

@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 10, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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:
  • OWNERS [ggiguash,kasturinarra]

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

@kasturinarra
Copy link
Contributor Author

/override ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-periodic ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-bootc-periodic
/verified by CI
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added 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 Jan 10, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 10, 2026
@openshift-ci-robot
Copy link

@kasturinarra: This PR has been marked as verified by CI.

Details

In response to this:

/override ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-periodic ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-bootc-periodic
/verified by CI
/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
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@kasturinarra: Overrode contexts on behalf of kasturinarra: ci/prow/e2e-aws-tests-bootc-periodic, ci/prow/e2e-aws-tests-bootc-periodic-arm, ci/prow/e2e-aws-tests-bootc-release, ci/prow/e2e-aws-tests-bootc-release-arm, ci/prow/e2e-aws-tests-periodic, ci/prow/e2e-aws-tests-release

Details

In response to this:

/override ci/prow/e2e-aws-tests-release ci/prow/e2e-aws-tests-periodic ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-bootc-periodic
/verified by CI
/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 kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

@kasturinarra: 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-release f3b6d24 link true /test e2e-aws-tests-release
ci/prow/e2e-aws-tests-bootc-release f3b6d24 link true /test e2e-aws-tests-bootc-release
ci/prow/e2e-aws-tests-periodic f3b6d24 link true /test e2e-aws-tests-periodic
ci/prow/e2e-aws-tests-bootc-periodic f3b6d24 link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests-bootc-periodic-arm f3b6d24 link true /test e2e-aws-tests-bootc-periodic-arm
ci/prow/e2e-aws-tests-bootc-release-arm f3b6d24 link true /test e2e-aws-tests-bootc-release-arm

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 14be064 into openshift:release-4.21 Jan 10, 2026
18 checks passed
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. 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants