[ PCA / OVM ] Inconsistent Handling of VM Manager Jobs
Last updated on JANUARY 11, 2018
Applies to:Private Cloud Appliance - Version 1.0.1 and later
Oracle VM - Version 3.0.1 and later
On Oracle VM Manager and Oracle Private Cloud Appliance, the behaviour of the VM Manager can become inconsistent.
Operations in the UI or CLI cause jobs to be submitted. Such jobs can remain in an incorrect state - for example a "Start Virtual Machine" operation causes a job to be started, but the job never shows as completed, and the Graphical User Interface continues to show status of "Starting" for the VM, even though the VM has actually started:
In the example of a VM start operation, when checking on the Oracle VM Server / Compute Node , using a command such as xm list , the Virtual Machine is indeed started, is reachable from its own IP address and all services on it are available. However, the VM Manager still displays it as starting.
The job appears to never finish and the Virtual Machine remains in starting state on the Oracle VM Manager.
Addition of a mis-configured element such as addition of a Storage Server or addition of new, or changes to LUNs on an existing Storage Server
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