Oracle VM Server Stays in "Starting" Status in the OVM Manager UI with OVMAPI_6000E Internal Error: OVMAPI_4021E Server discover conflict
(Doc ID 2306150.1)
Last updated on AUGUST 16, 2023
Applies to:Oracle Cloud Infrastructure - Version N/A and later
Oracle VM - Version 3.3.1 to 3.4.5 [Release OVM33 to OVM34]
Private Cloud Appliance - Version 2.4.3 to 2.4.3 [Release 2.0]
OVM Server is showing status as "Starting" at Servers & VMs tab Server's.
The server icon at top left panel showing as partial green, exactly as follows:
After refresh the OVM Server using OVMCLI the server shows the following error:
# ssh admin@localhost -p 10000
OVM>list server Command: list server Status: Success Time: 2017-09-15 09:34:18,461 CST Data: id:53:71:b2:c4:4e:65:11:e6:81:c8:fc:0e:04:b7:21:00 name:support5.oracle.com id:44:45:4c:4c:31:00:10:4e:80:57:b1:c0:4f:48:51:31 name:suppor8.oracle.com id:4c:4c:45:44:00:35:37:10:80:54:c3:c0:4f:48:53:31 name:support21.oracle.com <<<<<<==== Affected Server
OVM> refresh server name=support21.oracle.com Command: refresh server name=support21.oracle.com Status: Failure Time: 2017-09-15 09:48:04,670 CST JobId: 1504277283966 Error Msg: Job failed on Core: OVMAPI_6000E Internal Error: OVMAPI_4021E Server discover conflict at IP address: 192.168.1.10. The manager already has a server: support21.oracle.com, at this IP address, with SMBIOS UUID: 72:11:5b:c1:fe:f6:e5:11:ab:65:08:94:ef:14:4b:8f. But the server now being discovered: unknown, at that same IP address, has a different SMBIOS UUID: c1:5b:11:72:f6:fe:11:e5:ab:65:08:94:ef:14:4b:8f. This can happen in these cases: 1) This server has the same IP address as another server. Please correct that on the servers. Or, 2) The SMBIOS UUID of this server has changed due to a server motherboard change. Please delete the server from the manager and then re-discover it. Or, 3) The SMBIOS UUID has changed due to moving the blade in the chassis and there is an incorrect blade chassis SMBIOS UUID setting which allows the UUID of the server to change with the slot. Please update the blade chassis's SMBIOS UUID settings and re-discover. [Thursday Sep 15 09:48:04 CST 2017]
- BIOS Firmware upgrade on OVM Server chasis.
- If the customer changes the eth0 network adapter in one of this systems, it could cause a new uuid in some cases.
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