USHIFT-6074: Add support on releases scenarios to use artifacts from konflux #5596
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@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:
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
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
/retest |
@ggiguash Very small difference. The only difference is the MicroShift version under test. In this PR, the bootc image is fetched from 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 |
@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 |
|
/retest |
openshift-ci-robot
added
the
verified
|
@agullon: This PR has been marked as verified by 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. |
|
@agullon: The 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. |
|
/verified remove |
openshift-ci-robot
removed
the
verified
|
@agullon: The 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. |
|
|
||
| # Set the release type to ec, rc or zstream | ||
| LATEST_RELEASE_TYPE="ec" | ||
| # Latest Release info |
There was a problem hiding this comment.
You should make appropriate changes to generate_common_version.py
There was a problem hiding this comment.
Yes, you are right, it got merge after this change. I'll do it.
test/bin/common_versions.sh
Outdated
| if [[ "${LATEST_RELEASE_TYPE}" == "ec" ]]; then | ||
| KONFLUX_LREL_RELEASE_IMAGE_URL="https://mirror.openshift.com/pub/openshift-v4/$(uname -m)/microshift/ocp-dev-preview/${LATEST_RELEASE_VERSION}/el9/bootc-pullspec.txt" | ||
| else | ||
| KONFLUX_LREL_RELEASE_IMAGE_URL="https://mirror.openshift.com/pub/openshift-v4/$(uname -m)/microshift/ocp/${LATEST_RELEASE_VERSION}/el9/bootc-pullspec.txt" | ||
| fi |
There was a problem hiding this comment.
We need to discuss this. Currently, pre-release bootc image references are published at openshift mirror, but this is not how we agreed with the ART team originally.
/hold
|
/hold until we agree with ART team a common place to share the MicroShift bootc images |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
/test e2e-aws-tests-bootc-release e2e-aws-tests-bootc-release-arm |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/retest |
1 similar comment
|
/retest |
|
@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:
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-merge-robot
added
the
needs-rebase
openshift-merge-robot
removed
the
needs-rebase
|
/test e2e-aws-tests |
Co-authored-by: Jon Cope <[email protected]>
Co-authored-by: Jon Cope <[email protected]>
|
/retest |
1 similar comment
|
/retest |
|
@agullon: The following tests failed, say
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. |
6 participants
Add 2 new scenarios to test latest released microshift-bootc image created from konflux. This image can be fetched from different places:
registry.redhat.ioregistry.stage.redhat.iohttps://mirror.openshift.com/pub/openshift-v4/${UNAME_M}/microshift/ocp-dev-preview/https://mirror.openshift.com/pub/openshift-v4/${UNAME_M}/microshift/ocp/