Add nightly-4.22-upgrade-from-stable-4.22 variant for stable-to-nightly upgrade testing#77382
Add nightly-4.22-upgrade-from-stable-4.22 variant for stable-to-nightly upgrade testing#77382rioliu-rh wants to merge 1 commit intoopenshift:mainfrom
Conversation
…ly upgrade testing The existing stable-4.22-upgrade-from-stable-4.22 variant sets OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY to empty string, which is correct for stable-to-stable upgrades where both images are signed. However this makes it unsuitable for stable-to-nightly upgrades where the nightly target image is unsigned. The new variant uses the step default (true) for that env var and sets releases.target to candidate nightly stream.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rioliu-rh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.22-automated-release-nightly-4.22-upgrade-from-stable-4.22-aws-ipi-f999 |
|
@rioliu-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@rioliu-rh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
Summary
Add a new ci-operator config variant
automated-release-nightly-4.22-upgrade-from-stable-4.22to support testing the upgrade path from 4.22 stable (EC) to 4.22 latest nightly.Problem
The existing
automated-release-stable-4.22-upgrade-from-stable-4.22variant was being used for nightly upgrade testing, but it explicitly setsOPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY: "", which overrides the step default of"true". This causes the ipi-install step to enforce Sigstore image signature policy, which blocks the subsequent upgrade to the unsigned nightly target image — resulting in theopenshift-config-operatorpod failing to roll out and the upgrade stalling at 0%.Changes
automated-release-nightly-4.22-upgrade-from-stable-4.22with:releases.latest: 4.22 stable prerelease (install base)releases.target: 4.22 nightly candidate (upgrade target)OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICYoverride — step default"true"allows unsigned nightly imagesJira
https://redhat.atlassian.net/browse/OCPERT-352