[PCA 2.x] How to Recover From a Failed OVM Manager Upgrade (Doc ID 2643380.1)

Last updated on JANUARY 12, 2025

Applies to:

Private Cloud Appliance - Version 2.3.1 to 2.4.3 [Release 2.0]
Linux x86-64

Goal

If during an upgrade to PCA 2.3.4 or later from a previous major release level - the upgrade of the "non-primary" OVM Manager fails, then remedial steps must be taken before the upgrade can be re-attempted.

Such a failure can lead to an impasse, with:

the non-primary running OVM Manager 3.4.5 / 3.4.6 software
the primary running OVM Manager software earlier than 3.4.5 / 3.4.6
the database on the shared storage being either at current or earlier release.

This document explains how to backout the failed upgrade so both management nodes are at the same software level.

Note: this document does not apply to minor patch level upgrades such as 2.4.3 to 2.4.3.x, or 2.4.3.x to 2.4.3.y.

Note: there may be other actions needed prior to attempting upgrade, such as ensuring all symbolic links to OVM Manager resources are in place.
See Doc ID 2550664.1 for further information