openshift
USHIFT-6074: Add support on releases scenarios to use artifacts from konflux
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/
@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.
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.
[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
- ~~OWNERS~~ [agullon]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/hold I'd like to understand how these are different from [email protected] and [email protected]?
@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.
@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 , 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: This PR has been marked as verified by ci/prow/e2e-aws-tests-bootc-release job and el96-lrel@ginkgo-tests test.
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.
@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.
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: The verified label has been removed.
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.
/hold until we agree with ART team a common place to share the MicroShift bootc images
@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.
In response to this:
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/
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: 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-arm | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-release-arm |
| ci/prow/e2e-aws-tests-arm | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-arm |
| ci/prow/e2e-aws-tests-periodic | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-periodic |
| ci/prow/e2e-aws-tests-release | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-release |
| ci/prow/e2e-aws-tests-bootc-release-arm | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-bootc-release-arm |
| ci/prow/e2e-aws-tests-bootc-periodic | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-bootc-periodic |
| ci/prow/e2e-aws-tests-bootc-release | 921b29e653c75cb802fbaea09bb5b4fc6dd15b3e | link | true | /test e2e-aws-tests-bootc-release |
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.