Oracle VM 3: How to Forcefully Delete an Unassigned Oracle VM server when Fails with "OVMAPI_4010E Attempt to send command: release_ownership"
(Doc ID 1916292.1)
Last updated on AUGUST 04, 2018
Applies to:
Oracle VM - Version 3.0.1 to 3.3.1 [Release OVM30 to OVM33]Linux x86-64
Symptoms
This note explains how to forcefully delete an unassigned Oracle VM server after a delete server operation fails with the error shown below. Take note of the word "Clustered" at the end of the second line in the error message below. This provides a clue that there is likely a problem with the pool file system on the failed Oracle VM server.
OVMAPI_4010E Attempt to send command: release_ownership to server: myserver17 failed.
OVMAPI_4004E Server Failed Command: release_ownership 0004fb000001000063823772361f87eb, Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:Cannot release server in membership state: Clustered
OVMAPI_4004E Server Failed Command: release_ownership 0004fb000001000063823772361f87eb, Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:Cannot release server in membership state: Clustered
The following screen shot shows what the error message will look like as seen from the Oracle VM Manager:
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 |
| Cause |
| Solution |