EMOC failed to create a vServer due to incorrect view of memory on compute nodes
(Doc ID 1682091.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Exalogic Elastic Cloud Software - Version 126.96.36.199.2 and later
Enterprise Manager Ops Center - Version 12cR2 (12.2) to 12cR2 (12.2) [Release 12.0]
Information in this document applies to any platform.
You are using an Exalogic system that is running on an Exalogic Elastic Cloud Software (EECS) version 188.8.131.52.2 that is deployed in a virtual configuration. You have changed the root password for one or more compute nodes and updated the corresponding credentials stored within Enterprise Manager OpsCenter Control (EMOC) as instructed by the following Oracle documentation:
Credentials Management Guide
Release EL X2-2, X3-2 and X4-2
Section 2.1.2, "Synchronizing Compute-Node root Passwords with Enterprise Manager Ops Center"
Which can be downloaded from an attachment provided by the following support note:
Oracle Exalogic Elastic Cloud - Credentials Management Guide
However, following this you may have observed one or more of the following symptoms when creating Guest Virtual Servers using the (EMOC) browser interface:
- you may have seen the vServer created on an unexpected node, where the level of free vCPU/Memory is less than on other nodes
- vServer creation sometimes fails because the selected node has significantly less memory free than would be expected to successfully start the vServer
- In the EMOC browser UI, after selecting the Oracle Virtual Server icon nested under a compute node in the "Assets" accordion panel:
then, in the "Summary" tab, the value listed for "Available Memory (RAM)" is significantly different to the command line for that compute node:expected value, which can be obtained by running the following command on the compute node:
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