Exapatch Fails Upgrading the Guest vServers Due to Grub Corruption When Doing Linux Virtual PSU Upgrade from April 2014 (188.8.131.52.1) to July 2014 (184.108.40.206.2)
(Doc ID 1957315.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.2 to 18.104.22.168.2
When doing Linux Exalogic Virtual Linux PSU upgrade from April 2014 PSU (EECS 22.214.171.124.1) to July 2014 PSU (EECS 126.96.36.199.2) issue of Exapatch failing when upgrading the Guest vServers is observed.
At the time of the issue Exapatch script will fail with following snippet.
Above snippet shows that the guest vserver was rebooted and it is not coming up.
Following are list of additional symptoms observed at the time of the issue.
- Restart of the guest vserver using xm commands will get stuck and xm console won't print any output.
- Re-starting guest vServer from OVMM console will start the vserver but it automatically stops in sometime.
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