Is it possible to downgrade a version in OpenShift Container Platform 4?
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Service on AWS (ROSA)
- 4
- Red Hat OpenShift Dedicated (OSD)
- 4
- Azure Red Hat OpenShift (ARO)
- 4
Issue
- Need to downgrade a version in OpenShift 4.
- An OCP 4 upgrade failed. How to revert the upgrade?
- After an OpenShift 4 upgrade, custom applications are not working. Is it possible to rollback the upgrade?
Resolution
Rolling back or downgrading the OpenShift 4 version is generally not supported. Only upgrading to a newer version is supported as noted in the documentation about the OpenShift Update Service. Refer also to how cluster updates work for more information about upgrades.
Note: if forcing a downgrade of an OpenShift 4 cluster, the cluster could become in a unsupported state and re-installing the cluster could be the only option. Stronger warnings for
ClusterVersionforce and rollbacks are being included by OCPBUGS-63311. The use of theforceparameter is highly discouraged and it should be avoided, as if there is a mistake with the version, or if the version is not validated, it can break the cluster.
If an upgrade fails, do not try to rollback and open a support case, including a must-gather from the cluster: gathering data about your cluster.
Downgrade OpenShift 4 to a previous minor version
Rolling back or downgrading the OpenShift version to an earlier minor release (the y in 4.y.z) is not supported due to the presence of multiple API and etcd changes introduced in newer minor versions.
Note: if a downgrade to a previous minor version (the
yin4.y.z) is forced, the cluster becomes in an unsupported state and it could be required to re-install the cluster.
Downgrade OpenShift 4 to a previous z-stream release
Starting with OpenShift 4.16, in limited cases Red Hat Support could help with z-stream rollbacks after checking there are no other options as explained in why unassisted z-rollback is not supported?.
IMPORTANT: the
z-streamis thezversion in4.y.z, and that assisted z-rollback is not applicable in any case for minor releases (theyin4.y.z).
Root Cause
In OpenShift 4, only upgrading to a newer version is supported. Reverting or rolling back an OCP 4 cluster to a previous version is not supported due to the presence of multiple API and etcd changes introduced in newer minor versions. Embracing the dynamism of Openshift, each new version brings forth impactful enhancements. To ensure a seamless transition, Red Hat advocate for thorough testing of custom applications on the latest Openshift release prior to updating any production clusters.
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.
Comments