Initiative Overview

RHOSO 18 Feature Release 2 enabled support for OCP 4.18 and while we had some manual testing of upgrading 4.16 to 4.18, we are now looping back to implement automated testing of OCP upgrades.

Goals

We will benefit from this by having ongoing awareness of issues that may arise from OCP changes, before we release RHOSO updates to customers.

Done

Acceptance criteria is the existence of one or more periodic CI jobs which test upgrading OCP while RHOSO is deployed.

The suggested scenario is:

1. Deploy OCP 4.16 (latest z-stream)
2. Deploy RHOSO (latest z-stream)
3. Run a reasonable set of Tempest tests to verify RHOSO is working
4. Upgrade OCP to 4.18 (latest z-stream)
5. Re-run the set of Tempest tests to confirm RHOSO is unaffected

We should also discuss whether the following scenario makes sense to explore:

1. Deploy OCP 4.X (where X is the latest version supported by RHOSO)
2. Deploy RHOSO (latest z-stream)
3. Run a reasonable set of Tempest tests
4. Upgrade OCP to 4.Y (where Y is the latest pre-release build passing OCP tests)
5. Re-run the set of Tempest tests

This second scenario would likely give us early warnings of disruptive changes coming from OCP.