Developer story
(One sentence describing this story from an end-user perspective.
As a developer, I want to add new CI job for release 4.12 branch to test test bundle upgrades so that the newly introduced upgrade test enable the validation of the proposed backport to block concurrent upgrades [1]
[1]https://github.com/openshift/windows-machine-config-operator/pull/1932#top
Description
Currently, we do not have a way to test bundle upgrade that simulate actual WMCO bundle upgrades in release-4.12. The CI docs for operator upgrade testing can be followed to add this job.
Additionally having a job, that independently tests upgrades will allow us to test upgrades regularly and detect upgrade issues sooner without having to make changes to workflows of other projects using our current e2e test suite.
Engineering Details
Target platform: Azure
reference PR for master branch
https://github.com/openshift/release/pull/45161
Acceptance Criteria
azure-e2e-upgrade CI job pass in release-4.12
azure-e2e-upgrade CI job marked as required
- blocks
-
OCPBUGS-23020 WMCO upgrade strategy fails to upgrade one node at a time
- Closed
- relates to
-
WINC-654 upgrade CI job to test bundle upgrades for WMCO
- Closed
-
WINC-950 [e2e] Create a CI job that tests WMCO upgrades triggered by an OCP upgrade
- Closed
- links to