After Restarting The Control Stack, vServers are not correctly displayed in EMOC under the Assets accordion panel and you can no longer login to the OVM BUI using valid credentials
(Doc ID 2212390.1)
Last updated on NOVEMBER 14, 2022
Applies to:
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 and laterInformation in this document applies to any platform.
Symptoms
You have recently stopped and restarted the ExalogicControl vServer, either:
- manually: via "reboot" from inside the vServer or "xm shutdown <DOMAIN ID>" and "xm create <PATH TO VM.CFG>"
---OR--- - automatically: via the ExaBR command ("/opt/exalogic-lctools/bin/exabr stop control-stack" and "/opt/exalogic-lctools/bin/exabr start control-stack"
After the restart you may notice one or more of the following symptoms:
- Within the Enterprise Manager OpsCenter Control (EMOC) browser based user interface (BUI), when you expand the "Assets" accordion panel and view the vServers running on specific compute nodes:
- all vServers show running on each node is listed with an amber status moniker rather than a green triangle one
- the list of vServers shown on each compute may not correlate with the output of "xm list" for that vServer as should be expected.
- all vServers show running on each node is listed with an amber status moniker rather than a green triangle one
-
If you try to create a new vServer via EMOC and though a job is created the "Clone Virtual Machine" task fails the following error:
Changes
None of the above symptoms were present immediately prior to stopping and restarting the ExalogicControl vServer and no other changes have been made since.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |