[PCA] A PCA upgrade abruptly stops without a clear error in the logs, for the Management node being upgraded
(Doc ID 2658901.1)
Last updated on APRIL 28, 2020
Applies to:Private Cloud Appliance - Version 2.3.4 and later
Information in this document applies to any platform.
On Oracle Private Cloud Appliance, during the upgrades, there are various files being updated over time. One of them is the log file in the following folder :
In the event of an Oracle VM upgrade failure, a meaningful error message is typically printed in this log, then the upgrade is "handed back" from the failed OVM Manager upgrade to the upgrader on the Master Management Node, which then attempts to roll the failed steps back.
If an upgrade fails during the Oracle VM Manager upgrade, an error message*should be* printed at the very end of the Oracle VM Manager log reporting the root cause of the failure to upgrade Oracle VM Manager, which in turn triggers a failure of the entire Private Cloud Appliance upgrade mechanism.
However, the log file abruptly ends, with no particular error being reported. However, back on the Master management node, an error about a Secure Shell (SSH) timeout is being printed.
This could be very misleading, because the error is absent from the actual Oracle VM Manager upgrade, or as a post-mortem analysis.
One could try to figure if the slave being upgraded did reboot (fence out of the o2cb cluster, or any other reboot reason) and that the timeout is due to an unexpected communication end in between master and slave.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document