-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
-
-
AUTOSCALE - Sprint 271
As a dev, it would probably be useful to add operator upgrade tests to the CRO to limit regressions.
We've already seen one bug come out of this as a result of not testing upgrades: https://issues.redhat.com/browse/OCPBUGS-54886
Unfortunately, testing this upgrades locally is not as easy as it was for the VPA operator, since we currently have somewhat outdated tooling in the repo. However, I've already tested local upgrades using operator-sdk and opm despite this, and it seems to work fine. We just need the extra plumbing and scripts.
DoD:
- PR on release repo to add new presubmit jobs to test upgrades (we might want to go add these to previous versions as well)
- PR(s) on operator repo to make it easier to test operator upgrades locally
-
- we probably should cherry pick these back to earlier branches (at least to 4.16+) to make it easier on us in the future
Any bugs we find as a result should be filed as a new OCPBUG.
- is related to
-
OCPBUGS-54886 Upgrading from 4.16 to 4.17 causes the Cluster Resource Override Operator to stop working
-
- Closed
-
- links to