Exalogic: Compute node patching issue due to /etc/system-fips file missing or renamed - Workaround reinstalling kernel
(Doc ID 2588523.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.4.0 and later Information in this document applies to any platform.
Symptoms
Patching of Compute node OS fails after "exapatch" timeout has been reached. This is due to the system crashing and continue to reboot in a loop. Console output is as follows:
At this stage the pre and post patching tasks have completed yet the system won't boot due to the kernel panic.
Changes
This is due to the file /etc/system-fips either missing or has been renamed. The renaming of this file could have occurred due to a known issue while backing up the Exalogic Control Backup. As a workaround to this problem KM note 2478353.1 has been written, where is suggested to rename this file.
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
