Epic Goal (ETA/target Sprint: 232 )

• OPCT target v0.3
• Feature: Upgrade to 4.(Y+1) and run conformance tests
• Documentation Updates
• Results automation using 'process'

Primary Priorities:

• Upgrade feature
• Bugs impacting 4.12

Sprint planning:

• Started at: 219
• ETA: 232
• Ended at: TBD

Why is this important?

• Partners are waiting to upgrade feature being worked to create the upgrade path from a validated release
• VCSP Program is expecting this feature as described:
  • "Upgrade - upgradeable to a minor (4.y) release
    • Partner is responsible for ensuring the cluster deployed using the partner-provided installation method can be updated to the next OpenShift minor release (e.g. 4.y release) or OpenShift Extended Update Support (EUS) release for EUS-to-EUS updates."

Scenarios

1. As a partner I would like validate the upgrade in OCP installed in my provider to 4.y+1 using OPCT. Considerations:
   1. Original cluster, 4.y, should be already passed in the validation process (another support case)
   2. The final results will be: the cluster is validated to upgrade from 4.y to 4.y+1, and the 4.y+1 will be validated by VCSP Program by OPCT tool
   3. We must be able to run upgrades in current supported releases (4.9, 4.10, 4.11 and 4.12)
2.  

Acceptance Criteria

• Upgrade Feature have been implemented
• Blocker bugs closed
• 'report' command have been implemented
• Documentation updated
• ...

Dependencies (internal and external)

1. Validation the steps by Engineering team (Scott)

Previous Work (Optional):

1. OPCT-90

Open questions::

1. …

Done Checklist (TBD)

• CI - CI is running, tests are automated and merged.
• DEV - code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - documentation merged: <link to meaningful PR or GitHub Issue>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - documentation merged: <link to meaningful PR>