Problem with second host (migrate, redeploy, etc.)

Community Support
1

Hello,

My frontend works fine, but I have some strange problems with second host.

Both are the same Debian Jessie v8
With the latest ONE Medusa

When second host has only opennebula-common and opennebula-node packages installed,
it generates some errors during trying to create a contextualization ISO.
Missing scripts, etc.

After installing third package opennebula such errors do not appear anymore but there are other problems.

Mon Jul 31 04:51:24 2017 [Z0][VM][I]: New state is ACTIVE
Mon Jul 31 04:51:24 2017 [Z0][VM][I]: New LCM state is PROLOG
Mon Jul 31 04:51:25 2017 [Z0][VM][I]: New LCM state is BOOT
Mon Jul 31 04:51:25 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/48/deployment.0
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: ExitCode: 0
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy ‘/var/lib/one//datastores/102/48/deployment.0’ ‘lucie’ 48 lucie
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/102/48/deployment.0
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: error: internal error: process exited while connecting to monitor: 2017-07-30T23:51:26.759675Z qemu-system-x86_64: -drive file=/var/lib/one//datastores/102/48/disk.0,format=qcow2,if=none,id=drive-virtio-disk0,cache=none: Could not open ‘/var/lib/one//datastores/102/48/disk.0’: Permission denied
Mon Jul 31 04:51:26 2017 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/102/48/deployment.0
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: ExitCode: 255
Mon Jul 31 04:51:26 2017 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Mon Jul 31 04:51:26 2017 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/102/48/deployment.0
Mon Jul 31 04:51:26 2017 [Z0][VM][I]: New LCM state is BOOT_FAILURE

2

-rw-r–r-- 1 oneadmin oneadmin 1003 Jul 31 04:51 deployment.0
lrwxrwxrwx 1 oneadmin oneadmin 67 Jul 31 04:51 disk.0 → /var/lib/one/datastores/103/27321e807c221ed36f08cedbf9eaa323.snap/0
lrwxrwxrwx 1 oneadmin oneadmin 65 Jul 31 04:51 disk.0.snap → /var/lib/one/datastores/103/27321e807c221ed36f08cedbf9eaa323.snap
-rw-r–r-- 1 oneadmin oneadmin 372736 Jul 31 04:51 disk.1

3

It is a shared qcow2 persistent image which works fine on another host (frontend)

4

executed
chmod 777 on datastore/102/XX

then click recover retry
and VM started fine

How can I fix permission automatically to more restrictive than 777 of course?