My Oracle Support Banner

Exalogic 2.0.6.4.0 Upgrade Known Issues (Doc ID 2814870.1)

Last updated on AUGUST 19, 2022

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.4.0 to 2.0.6.4.0
Linux x86-64
Oracle Virtual Server x86-64



Purpose

This document provides list of known issues that can be encountered when upgrading Exalogic Virtual racks 2.0.6.3.X racks to 2.0.6.4.0 using Upgrade kit.

Scope

Exalogic Virtual racks 2.0.6.3.X upgraded to 2.0.6.4.0 using Upgrade kit.

Details

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
Purpose
Scope
Details
 OVMM 3.4.5 shows an error icon for Compute node hosting PXE VM (exalogic-pxe-vm) in Step 7
 Running time unavailable and server version shows as 3.2.11 for reimaged nodes in EMOC BUI (after the upgrade)
 EXAPASSWD FAILED TO SYNC COMPUTE NODE ILOM PASSWORDS IN EMOC
 EXACHK REPORT ON EXACHK RUN AT THE END OF POST UPGRADE SHOWS INTERFACE DOWN WARNING IN CONTROL VSERVERS SECTION OF THE REPORT
 Step 4.B and 10.B Image: Reimaging is stuck at OS Selection screen
 STEP 4.B & 10.B ILOM SP CONSOLE OF THE COMPUTE NODE BEING REIMAGED SHOWS NON READABLE CHARACTERS
 Step 10.A.ii. Pre-Image: Guest vServer PrePatchCheck failed.
 Exalogic Virtual:: Server now being discovered: unknown, at that same IP address, has a different SMBIOS UUID
 Exalogic Virtual:: Server Pool mismatch while running post-imaging step for Compute Node
 Exalogic Virtual:Warning "Server is missing a pool FS mount" Warning Message In OVM Manager BUI Console In Racks Upgraded To 2.0.6.4.0 From 2.0.6.3.X Using Upgrade Kit
 Exalogic Virtual 2.0.6.4.0 Upgrade: After ILOM Upgrade Compute Node Fails To Boot Due To Incorrect UUID Entries in /etc/fstab
 Step 4.B and 10.B Image: Reimaging is stuck with 'Error downloading Kickstart file' on ILOM console
 Delete virtual IP cleanup run in step 14 reports an error and exits
 Step 4.C Post-Image:  Guest VM Boots With Older Kernel During 2.0.6.4 Upgrade
 Step 4.C Post-Image: File "/etc/ntp.conf" of all DOM0s were pointing to control VM ip instead of pointing to NTP Servers.
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.