This update is not applicable for HVM domU HVM domU
(Doc ID 2725110.1)
Last updated on MARCH 16, 2021
Applies to:Oracle Exadata Storage Server Software - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
exadata.computenode.post step fails while updating VM on virtualizes Exadata (X7-2).
patchmgr starts exadata.computenode.post step and waits for this step to complete within the defined timeout. But this step does not run properly since exadata.computenode.post.log show message "This update is not applicable for HVM domU HVM domU" and quits without doing anything at all. After the timeout expires, patchmgr rolls back to former image backup.
The problem seems to be that the scripts (obviously /opt/oracle.cellos/image_functions) depends on the system-product-name gathered from dmidecode and expect a value of "HVM domU". But the message shows this value doubled "HVM domU HVM domU".
exadata.computenode.post.trc this this output with the wrong value too:
[2020-10-29 23:52:39 +0100][TRACE][/opt/oracle.cellos/image_functions - 1074][source] The system model is: HVM domU HVM domU
The problem was seen only on one VM other VM succeeded without problem.
DB Node Update to 126.96.36.199.0 fails in exadata.computenode.post Step and rollbacks to old version.
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