Epic Goal

• Agree upon OpenShift Paused Worker Pool Upgrade test jobs and implement them. These tests are meant to replicate the skipped reboot pattern that we may deliver for EUS to EUS upgrades illustrated in this slide https://docs.google.com/presentation/d/1PJvN6-hLm9Vr8KuecMmiyk9J5vszGDcTAsppKLUet70/edit#slide=id.gbab5de315b_0_112

Why is this important?

• This will inform us as to the types of problems which arise in paused worker pool upgrades across two minor versions
• This will inform us as to the viability of such

Scenarios

1. Revamp 4.x -> 4.x+1 -> 4.x+2 Upgrade jobs
2. Add a step which pauses Worker pool in 4.x and unpauses on 4.x+2 with additional testing at appropriate steps

Defining required testing pattern for Paused Worker Pool upgrades document at https://docs.google.com/document/d/1mHNMb61LY57EspItsgIM_CceXgQuC__wqmAW1j48awE/edit#

Need to get buy in from all teams with host components including but not limited to RHCOS, MCO, SDN, Node, Container Engines, PSAP, Storage (CSI), Cloud Infra

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - None, this is just a testing and data collection effort at this point in time. Later decisions will be made with regard to the viability of supporting this mode with customers
• ...

Open questions::

1. The linked document above proposes to identify the requisite testing, we should discuss that in the linked document

Done Checklist

• CI - CI is running, tests are automated and merged.