A job listed in Oracle VM Manager can have any of the states defined in Table 8.2, “Job States”.
Table 8.2 Job States
Job State | Definition |
|---|---|
Completed | The job has completed. |
In Progress | The job is in progress. |
Aborted | The job has been aborted. Oracle VM Manager has rolled-back to its previous state and all locks have been released. |
Failed | The job has failed. Oracle VM Manager has rolled-back to its previous state and all locks have been released. |
Child Queued | The job has spawned a child job. This child job is in queue but is not running yet. The parent job is waiting for all child jobs to complete. |
Child Running | The job has spawned a child job. This child job is currently running. The parent job is waiting for all child jobs to complete. |
Some job operations, such as renaming an object, complete quickly. Others, such as adjusting the memory used by a virtual machine, take longer. Monitoring Job States allows you to understand how a job is progressing.
If a job is running or fails to complete, you can abort the job to cancel it. For example, a virtual machine or Oracle VM Server may be in an unresponsive state and fail to respond to a start or stop request. The appropriate action is to abort the job. When a job is cancelled in this way, its state changes to Aborted. See Abort Jobs in the Oracle VM Manager User's Guide for information on aborting jobs.
Jobs may hang or remain In Progress every time a virtual machine is started or stopped. A paravirtual machine may be in an unresponsive state for a variety of reasons and consequently fail to respond to a start or stop request. The appropriate action in this case is to abort the job. For example, when starting a PVM virtual machine using PXE type boot with an invalid network URL, this causes the virtual machine status to be In Progress indefinitely. To resolve this, abort the virtual machine start job. Edit the virtual machine and provide the correct URL.
If a job has a Failed state, more information is available for the job, usually indicating the reason for failure. This information is accessible using any of the interfaces provided for Oracle VM Manager.
Some jobs may spawn child jobs. In this case, the parent job will have the status Child Queued or Child Running. The parent job must wait until all spawned child jobs are completed before it is able to report its status. This is typical in situations where multiple actions must be performed on different objects within Oracle VM Manager. For instance, when presenting a repository to multiple servers, a parent job is created to handle the action and report on its overall status, but subsequent child jobs are spawned to actually carry out the task on each server.
If a job seems to hang in a Child Queued state for an extended period of time, check the reachability of your server. Oracle VM Manager continues to try to execute a job even if the server is unreachable. It does not stop attempting to run the job until the job has been completed or the job is aborted. This can cause the job queue to lock so that subsequent actions within Oracle VM Manager are not added to the job queue. If this happens, you may need to abort the job that is hanging in this state to free up the job queue.
If you log out of the Oracle VM Manager Web Interface and there are pending or in progress jobs, a warning is displayed confirming you want to log out. If you do log out, any pending or in progress jobs are cancelled. If there is a UI timeout, pending and in progress jobs continue.