Article ID: 120417, created on Mar 4, 2014, last review on May 11, 2014

  • Applies to:
  • Operations Automation
  • Panels
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

  • Migration of a container fails with the following error:

    Can't move/copy CT#133 -> CT#133, [], [] : vztt_get_vzdir() error, retcode=49
    
  • Attaching strace to the vzmigrate operation, the following messages can be seen in the output:

    [root@pvc~]# strace -vvvtTfs4096 -o vzmigrate.str.log vzmigrate root@'10.0.1.11' 101
    [root@pvc~]# less vzmigrate.str.log
    ...
    702239 21:31:19 access("/vz/template/fedora/17/x86_64/pm/", F_OK) = 0 <0.000013>
    702239 21:31:19 stat("/vz/pkgenv/rpm49db5x64/usr/lib64//python2.2", 0x7fffe5ef0350) = -1 ENOENT (No such file or directory) <0.000011>
    702239 21:31:19 stat("/vz/pkgenv/rpm49db5x64/usr/lib64//python2.3", 0x7fffe5ef0350) = -1 ENOENT (No such file or directory) <0.000011>
    702239 21:31:19 stat("/vz/pkgenv/rpm49db5x64/usr/lib64//python2.4", 0x7fffe5ef0350) = -1 ENOENT (No such file or directory) <0.000011>
    ...
    

Cause

The destination node is not updated and is missing the package manager, required for the OS template the migrated container is based on.

Resolution

Install the tools updates on the destination node:

For PVC or PSBM :

# vzup2date -s -m batch install --tools

For PCS :

# yum install vzpkgenv*

Search Words

unable to create cloud server from image

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 0dd5b9380c7d4884d77587f3eb0fa8ef 614fd0b754f34d5efe9627f2057b8642 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF