Article ID: 117842, created on Oct 10, 2013, last review on Apr 13, 2017

  • Applies to:
  • Operations Automation


The Operations Automation (OA) Provider or Customer Control Panel shows the incorrect location or status for the Cloud Infrastructure (CI) server (Virtual Environment, or VE).

For example, the Provider initiates a migration of a CI server between Hardware Nodes. The server is successfully migrated and is up-and-running on the target Node.

However, the OA Control Panel still shows the server as being located on the source Hardware Node and the status of the CI server is incorrect: "Migration failed", "Migration in progress", or "Failed to start".

A similar problem may be caused by CI server backup or restore operations, or by creating a VM image.


There are several possible causes of this issue:

  • The OACI Instance Manager (IM) server did not get a callback or was not able to process the callback from the Hardware Node after the requested operation (backup, restore, migration) was completed. For example, the callback timed out.
  • The IM server was restarted, or crashed while processing a callback from the corresponding Hardware Node.
  • There was a node crash and VE failed to get relocated by the backend High Availability routines.



    In order to synchronize the location of the VE, it is needed to move it manually to the hardware node, to which it is bound in Control Panel. Use Virtuzzo utilities to do that directly on the hardware node:

    • To relocate a container (CT):

      # pmigrate c [VEID|UUID] c [TARGET_NODE] --online

      where [VEID|UUID] - either the container ID (displayed by vzlist) or the container UUID (displayed by prlctl list) --online option is used to initiate a "hot" migration to minimize the downtime of VE services

      Real-life example:

      # pmigrate c 101 c --online
    • To relocate a virtual machine (VM):

      # pmigrate v [VM_NAME|UUID] v [TARGET_NODE]

      where [VM_NAME|UUID] - either the name or UUID of the virtual machine (displayed by prlctl list)

      Real-life example:

      # pmigrate v test_vm v

      Note: for virtual machines, "online" migration mode is initiated by default in case the VM is in running state.

  2. STATUS.

    In order to synchronize the status of the VE, use Virtuozzo VE management utilities to bring the VE to the same state, as it is displayed in CP. In case of any difficulties, contact Odin Technical Support to resolve the situation.

    If a VM has moved to UNCERTAIN state, it is enough to press the action button in CP that corresponds to the last actual state per VE history: press 'start' if it was RUNNING, press 'stop' if it was STOPPED. The state will get synced afterwards and no actual actions will be done to the VE.

  3. UUID mismatch.

    Sometimes after manual actions with VEs on Virtuozzo backend, the VE may end up with wrong UUID, as opposed to OACI IM records. As a result, there's the following error logged to /var/log/IM/PACI-im-errors.log:

    2016-09-03 00:00:18,502 () ERROR SnmpManagerImpl [VF executor thread #28] - VE uuid doesn't match: 2a90296c-3f8a-4182-a9a6-00917e3be9cb != f2bcb6db-72bc-4913-917e-a89486b2c0ee for VeId [customerId=1010101, name=server-1002003], update ignored

    Follow these steps to fix the problem:

    1. At convenient time, suspend the VM (all OS operations inside the VM will get freezed):

      # prlctl suspend 1010101.server-1002003
    2. Unregister it:

      # prlctl unregister 1010101.server-1002003
    3. Register the VM back with the required UUID:

      # prlctl register /pcs/1010101.server-1002003.pvm --uuid 2a90296c-3f8a-4182-a9a6-00917e3be9cb

      Note: for CT technology type, the path will contain VEID, e.g. /pcs/123.

    4. Resume the VM:

      # prlctl resume 1010101.server-1002003

Search Words


Import container failed

PACI IM manager not starting

PACI migration hangs

node was rebooted


CI server

paci migrate

Not able to resize disk and container hanging in "starting" status


paci Creation in progress

status incorrect


status mismatch

vm in unknown state


restore backup

VE uuid doesn't match

Virtual Machine in Unknown state

wrong location after migration

Virtual Machine in Unknown State

Unknown state


Migration failed

backing up status paci

terracotta ehache

backup in progress paci

UNCERTAIN status for VM's

node2 backup always failing and in Unknown state

instance manager shutdown

wrong location of the cloud server

wrong location of cloud server after migration

Backups are missing, not created and still in progress

vm stuck in Failed to restore state

stop in progress

Virtual Machine in Unknown stat

The requested operation cannot be performed on the Server in-web-a-08 while it is in the current state.

vm in unknow state

faile ve

status CT mismatch

PACI server in unknown state

paci status

Servers have the wrong state in PACI

server stuck backup in progress

Server is in unknown state

PACI backup is failing

PACI in unknown state


PACI VE status inconsistency

migration in progress

vm in unknow state7

paci stuck wrong status

VE status inconsistency

Backing up


Server in unkown state

VE is busy


unable to migrate cloud server

Server was not found virtualization node


paci failover inconsistency

import failed

Virtual servers in Unknown State

bckup in progress

terracotta ehcache

vm migration

Backup in progress


transitional status

Virtual Machine in Stopped State


caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF