How to upgrade RHODF while doing RHOCP EUS-to-EUS upgrade

Environment

• Red Hat OpenShift Data Foundation (RHODF)
  • 4
• Red Hat OpenShift Container Platform (RHOCP)
  • 4
• EUS-to-EUS upgrade

Issue

• What steps need to be followed to upgrade RHODF while doing an RHOCP EUS upgrade?

Resolution

Refer to the OpenShift documentation for performing a Control Plane Only update for layered products and Operators installed through Operator Lifecycle Manager.

As an example, while upgrading from RHOCP v4.16 to v4.18:

0. Switch to desired EUS channel
1. Pause all non-master machine pools (RHODF worker, infra, etc.).
2. Partially Upgrade of RHOCP from 4.16.z to 4.17.z, with worker nodes in pause
3. Upgrade RHODF and Local Storage operator to 4.17.z
4. Partially Upgrade of RHOCP from 4.17.z to 4.18.z, with worker nodes in pause
5. Upgrade RHODF and Local Storage operator to 4.18.z
6. Unpause all non-master machine pools (RHODF worker, infra, etc.) to allow them to be upgraded to 4.18.z.

The key thing here is that RHODF must be upgraded along with RHOCP to ensure compatibility is always maintained.

Root Cause

RHODF must be upgraded along with RHOCP to ensure compatibility is always maintained.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.