Failed to identify the default kernel version - this is likely because the boot loader configuration does NOT contain any default kernel
search cancel

Failed to identify the default kernel version - this is likely because the boot loader configuration does NOT contain any default kernel

book

Article ID: 275663

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Message below when trying to access vApp

Failed to identify the default kernel version - this is likely because the boot loader configuration does NOT contain any default kernel
The operating system may not be able to start if this server is rebooted!

****************************************************************
*** PLEASE DO NOT REBOOT YOUR SYSTEM, AND CONTACT CA SUPPORT ***
****************************************************************

Environment

Release : 14.3 CP2

Resolution

Review with your Data Center network team on any potential recent hardware failures, power surges, and outages in the Data Center.

Root cause is sadly a confirmed OS corruption potentially by a possible power surge or network issue at the Data Center causing this type of corruption on these two nodes.  From the vApp side, there are no commands or configurations that we can run to fix this. 

You will need to restore from a backup or a fresh vApp deployment on a new virtual system