Exalogic Virtual: EMOC Is Not Utilizing A Specific Compute Node When Creating/Starting vServers When Node Is Not Blacklisted For vserver_placement
Last updated on JUNE 22, 2016
Applies to:Oracle Exalogic Elastic Cloud Software - Version 184.108.40.206.0 and later
Oracle Virtual Server x86-64
You have an Exalogic Virtual system running Exalogic Elastic Cloud Software (EECS) as a virtual deployment, where you are seeing unexpected behavior with respect to the compute nodes that the Enterprise Manager OpsCenter (EMOC) BUI is selecting for the placement of newly created or restarted vServers: EMOC is not electing to place the started vServer on certain nodes, even though the nodes have sufficient levels of free vCPU and RAM to host it and those nodes have not been manually blacklisted against vServer placement by the addition of a vserver_placement.ignore_node tag that has been set to TRUE.
On occasion, when submitting a "Create vServer" or "Start Guest" operation from the last screen of the respective wizard, you may experience an error similar to the following with no EMOC job being created, even though you have nodes that have sufficient free vCPU and RAM to allow the vServer to be started on one of the nodes:
When you encounter this unexpected behavior then, if you access the BUI for the Oracle Virtual Machine Manager (OVMM) and expand each Server Pool item in the tree menu within the left pane, you do not see a green "play" moniker on the icon for the compute nodes that EMOC has elected not to use. In addition, if you select a pool entry containing such a server and select the "Servers" perspective in the drop down menu in the main pane, in Status column for nodes without the green triangle you may see a status such as "Stopped (Error)" or "Running (Error)".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms