Article ID: 120356, created on Feb 27, 2014, last review on May 4, 2014

  • Applies to:
  • Odin Business Automation Standard 4.5
  • Odin Business Automation Standard 4.3

Symptoms

I tried to recreate a container after I found it "conflicted". The container remain in status "Ordered" and the following error is shown on the container's General Settings page:

Top > Service Director > Virtuozzo Manager > Containers > #CT_ID

Failed to create this Container, because a Container with the same ID was found on the node. Please remove the conflicting Container from the node and try to create the environment again.

Cause

The order cannot be processed and the container cannot not be created in the node because a container with the same ID already exists - this is the same container, but it's broken (it cannot be started):

C:\Users\Administrator>vzlist CT_ID
VEID NPROC STATUS IP_ADDR HOSTNAME
CT_ID -- stopped 123.123.123.123 CT_ID

C:\Users\Administrator>vzctl start CT_ID
Starting container ...
Parallels Virtuozzo Containers API function call 'VZVolumeMountExW' failed (D:\v
z\Private\CT_ID\root.efd, {a3bbcccf-7090-4185-b3fe-5ca603597516}) err = 32
Parallels Virtuozzo Containers API function call 'dq_mount' failed
Cannot set disk quota for container CT_ID
Cannot mount disk for container CT_ID

Resolution

Resolve the issue according to Unable to start container: "VZVolumeMountExW failed" and start the container in HW node. When the container was started in the HW node, consider dumping it with "vzbackup localhost -e CT_ID", just in case.

To synchronize containers status with PBA-S, run periodic task "Detected newly appeared Virtuozzo VE conflicts":

Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue > Detected newly appeared Virtuozzo VE conflicts > Run now

If after that the container remain in status "Ordered", then try recreating it with "Recreate".

Search Words

cannot recreate a container

Cannot mount disk for container

Failed to create this Container, because a Container with the same ID was found on the node

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e 807e9c1dc97aefd951b912a17e50c428

Email subscription for changes to this article
Save as PDF