Cannot access backing file?

Community Support
1

Hi,

I detached an image from my VM to clone it. For that I shutted the machine down. After Cloning the image I reattached the device to the VM again and liked to boot it. Now Open Nebula ist complaining that the backing file can not be accessed:

    Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: ExitCode: 0
    Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
    Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/home/one/datastores/107/39/deployment.19' 'jupiter.alsdienst.de' 39 jupiter.alsdienst.de
    Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: error: Failed to create domain from /home/one/datastores/107/39/deployment.19 
    Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: error: Cannot access backing file '/home/one/datastores/105/6295bcb78bb203a8895e40703de94518' of storage file '/home/one/datastores/107/39/disk.2' (as uid:9869, gid:9869):    No such file or directory
   Sun Mar 26 12:43:47 2017 [Z0][VMM][E]: Could not create domain from /home/one/datastores/107/39/deployment.19 
   Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: ExitCode: 255 
   Sun Mar 26 12:43:47 2017 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
   Sun Mar 26 12:43:47 2017 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /home/one/datastores/107/39/deployment.19
   Sun Mar 26 12:43:47 2017 [Z0][VM][I]: New state is POWEROFF
   Sun Mar 26 12:43:47 2017 [Z0][VM][I]: New LCM state is LCM_INIT

But on the host machine it looks this way:

root@jupiter /home/one/datastores/107/39 # ll
total 468
drwxrwxr-x 2 oneadmin oneadmin   4096 Mar 26 12:43 ./
drwxr-xr-x 7 oneadmin oneadmin   4096 Mar 26 12:29 ../
-rw-rw-r-- 1 oneadmin oneadmin   1092 Feb 22 19:55 deployment.0
-rw-rw-r-- 1 oneadmin oneadmin   1092 Feb 22 20:26 deployment.1
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 12:30 deployment.10
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 12:30 deployment.11
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 12:30 deployment.12
-rw-rw-r-- 1 oneadmin oneadmin   1219 Mar 26 12:31 deployment.13
-rw-rw-r-- 1 oneadmin oneadmin   1219 Mar 26 12:32 deployment.14
-rw-rw-r-- 1 oneadmin oneadmin   1219 Mar 26 12:38 deployment.15
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 12:40 deployment.16
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 12:42 deployment.17
-rw-rw-r-- 1 oneadmin oneadmin   1254 Mar 26 12:43 deployment.18
-rw-rw-r-- 1 oneadmin oneadmin   1219 Mar 26 12:43 deployment.19
-rw-rw-r-- 1 oneadmin oneadmin   1280 Feb 22 20:30 deployment.2
-rw-rw-r-- 1 oneadmin oneadmin   1259 Feb 26 01:08 deployment.3
-rw-rw-r-- 1 oneadmin oneadmin   1259 Feb 26 01:13 deployment.4
-rw-rw-r-- 1 oneadmin oneadmin   1071 Feb 26 01:18 deployment.5
-rw-rw-r-- 1 oneadmin oneadmin   1280 Mar 26 09:09 deployment.6
-rw-rw-r-- 1 oneadmin oneadmin   1259 Mar 26 09:15 deployment.7
-rw-rw-r-- 1 oneadmin oneadmin   1280 Mar 26 09:16 deployment.8
-rw-rw-r-- 1 oneadmin oneadmin   1240 Mar 26 09:41 deployment.9
lrwxrwxrwx 1 oneadmin oneadmin     64 Feb 22 19:55 disk.0 -> /home/one/datastores/105/8090584c6518de949aafaf6987293abc.snap/0
lrwxrwxrwx 1 oneadmin oneadmin     62 Feb 22 19:55 disk.0.snap -> /home/one/datastores/105/8090584c6518de949aafaf6987293abc.snap/
-rw-r--r-- 1 oneadmin oneadmin 372736 Mar 26 12:43 disk.1
lrwxrwxrwx 1 oneadmin oneadmin     64 Mar 26 12:43 disk.2 -> /home/one/datastores/105/2e9b640139fc40922280f8624f8e50d0.snap/0
lrwxrwxrwx 1 oneadmin oneadmin     62 Mar 26 12:43 disk.2.snap -> /home/one/datastores/105/2e9b640139fc40922280f8624f8e50d0.snap/

The link disk.2 is pointing to a file starting with “2e9” and not with “629”. Why Open Nebula tries to access the file ‘/home/one/datastores/105/6295bcb78bb203a8895e40703de94518’.

Is there another place where Open Nebula caches these links?