USHIFT-6074: Add support on releases scenarios to use artifacts from konflux by agullon · Pull Request #5596 · openshift/microshift

agullon · 2025-10-10T13:09:22Z

Add 2 new scenarios to test latest released microshift-bootc image created from konflux. This image can be fetched from different places:

released zstream versions: registry.redhat.io
existing but not released yet zstream versions: registry.stage.redhat.io
EC versions: https://mirror.openshift.com/pub/openshift-v4/${UNAME_M}/microshift/ocp-dev-preview/
RC versions: https://mirror.openshift.com/pub/openshift-v4/${UNAME_M}/microshift/ocp/

Summary by CodeRabbit

New Features
- Auto-resolve and export LATEST_RELEASE_IMAGE_URL for dynamic base-image selection.
- Export additional minor-version and release-related variables for downstream flows.
Tests
- Added published-image test scenarios that validate resolved release images with signature verification and firewall prep.
- Removed legacy published-image test scenarios.
Other
- Templates now conditionally use the resolved release image as the build base.

openshift-ci-robot · 2025-10-10T13:09:27Z

@agullon: This pull request references USHIFT-6074 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:

Add 2 new scenarios to test latest released microshift bootc image available from mirror.openshift.com repo

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 · 2025-10-10T14:07:37Z

/hold
I'd like to understand how these are different from el96-crel@published-images-standard1.sh and el96-crel@published-images-standard2.sh?

agullon · 2025-10-10T14:12:29Z

/retest

agullon · 2025-10-10T15:32:39Z

/hold I'd like to understand how these are different from el96-crel@published-images-standard1.sh and el96-crel@published-images-standard2.sh?

@ggiguash Very small difference. The only difference is the MicroShift version under test. In this PR, the bootc image is fetched from mirror.openshift.com repo using the version of the latest RPM packages internally published on brew. The purpose of these 2 new scenarios is to validate the bootc image built from konflux is working as expected before QE approval for every z-stream version.

In periodics scenarios the version under test is fetched from final repositories, meaning it's already GA published. There is an exception to the previous statement: if no z-stream exist yet (for example in release-4.20 and release-4.21 at this moment) mirror.openshift.com repo is used instead of final repos.

ggiguash · 2025-10-11T05:49:35Z

@agullon , can you clarify this a bit more?
Looking here for example, the existng tests first try pulling from the mirror.openshift.com if the current version is configured to use the mirror. Otherwise, they fall back to using the GA'ed images.

agullon · 2025-10-13T07:49:13Z

@agullon , can you clarify this a bit more? Looking here for example, the existng tests first try pulling from the mirror.openshift.com if the current version is configured to use the mirror. Otherwise, they fall back to using the GA'ed images.

@ggiguash The goal of this PR is to test, during the Release Testing process, the MicroShfit bootc images produced by konflux before they are GA. We need to validate the artifacts before they are GA. For this reason, in the code added for this PR there's no a fallback mechanism into the GA'ed images. Instead, the bootc images under test are always fecthed from mirror.openshift.com repo.

agullon · 2025-10-13T11:47:07Z

/retest

openshift-ci-robot · 2025-10-14T14:00:09Z

@agullon: This PR has been marked as verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test.

Details

In response to this:

/verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test

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-robot · 2025-10-14T14:01:33Z

@agullon: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified cancel

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.

agullon · 2025-10-14T14:02:04Z

/verified remove

openshift-ci-robot · 2025-10-14T14:02:17Z

@agullon: The verified label has been removed.

Details

In response to this:

/verified remove

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.

test/bin/common_versions.sh

agullon · 2025-10-21T08:50:04Z

/hold until we agree with ART team a common place to share the MicroShift bootc images

agullon · 2025-11-25T11:54:41Z

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

agullon · 2026-02-23T07:45:23Z

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

test/scenarios-bootc/releases/el96-lrel@published-images-standard1.sh

test/bin/scenario.sh

kasturinarra · 2026-02-24T10:08:20Z

/lgtm

openshift-ci · 2026-02-24T10:08:59Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, 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~~ [agullon,kasturinarra]

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

openshift-ci · 2026-02-24T10:31:48Z

New changes are detected. LGTM label has been removed.

…konflux pre-commit.check-secrets: ENABLED

agullon · 2026-02-24T18:04:02Z

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

test/scenarios-bootc/releases/el96-lrel@published-images-standard1.sh

openshift-ci · 2026-02-24T20:03:15Z

@agullon: 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-release	`f71f3ec`	link	true	`/test e2e-aws-tests-bootc-release`
ci/prow/e2e-aws-tests-release	`f71f3ec`	link	true	`/test e2e-aws-tests-release`
ci/prow/e2e-aws-tests-bootc-release-arm	`f71f3ec`	link	true	`/test e2e-aws-tests-bootc-release-arm`
ci/prow/e2e-aws-tests-release-arm	`f71f3ec`	link	true	`/test e2e-aws-tests-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-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 10, 2025

openshift-ci bot requested review from copejon and jogeo October 10, 2025 13:10

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 10, 2025

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 10, 2025

agullon force-pushed the USHIFT-6074 branch from 3bd8327 to bda922e Compare October 10, 2025 17:28

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025

openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025

pmtk reviewed Oct 16, 2025

View reviewed changes

test/bin/common_versions.sh Outdated Show resolved Hide resolved

ggiguash reviewed Oct 16, 2025

View reviewed changes

test/bin/common_versions.sh Outdated Show resolved Hide resolved

agullon marked this pull request as draft November 18, 2025 13:16

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 Nov 18, 2025

agullon force-pushed the USHIFT-6074 branch from 818d599 to 71f8364 Compare November 25, 2025 11:52

agullon marked this pull request as ready for review November 25, 2025 11:54

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 Nov 25, 2025

agullon marked this pull request as draft November 25, 2025 11:55

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 Nov 25, 2025

agullon force-pushed the USHIFT-6074 branch from eb3af4d to fa3f1c5 Compare February 23, 2026 07:45

ggiguash suggested changes Feb 23, 2026

View reviewed changes

test/scenarios-bootc/releases/el96-lrel@published-images-standard1.sh Outdated Show resolved Hide resolved

test/bin/scenario.sh Show resolved Hide resolved

agullon force-pushed the USHIFT-6074 branch from c25986a to 11cf13c Compare February 23, 2026 11:18