Triple o Quickstart fail
Tuesday 13 February 2018 08:43:16 +0000 (0:00:00.183) 0:02:59.980 ** fatal: [cube]: FAILED! => {"changed": true, "cmd": "virt-customize --run /home/stack/repo_setup.sh -a /home/stack/overcloud-full.qcow2 > /home/stack/_home_stack_repo_setup.sh.log 2>&1", "delta": "0:00:00.610437", "end": "2018-02-13 08:43:17.627506", "failed": true, "msg": "non-zero return code", "rc": 1, "start": "2018-02-13 08:43:17.017069", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
seems to be related to the permissions on /home/stack
[root@cube pete]# ls -ld /home/stack/ drwx------ 9 stack stack 4096 Feb 13 08:43 /home/stack/
[root@cube pete]# sudo virt-customize --run /home/stack/repo_setup.sh -a /home/stack/overcloud-full.qcow2 [ 0.0] Examining the guest ... virt-customize: error: libguestfs error: could not create appliance through libvirt.
Try running qemu directly without libvirt using this environment variable: export LIBGUESTFS_BACKEND=direct
Original error from libvirt: Cannot access storage file '/home/stack/overcloud-full.qcow2' (as uid:107, gid:107): Permission denied
setting to a more permissive 755, gives: [root@cube pete]# chmod 755 /home/stack/ [root@cube pete]# sudo virt-customize --run /home/stack/repo_setup.sh -a /home/stack/overcloud-full.qcow2 [ 0.0] Examining the guest ... [ 2.8] Setting a random seed [ 2.8] Running: /home/stack/repo_setup.sh ...
re-running the quickstart, resets the /home/stack permissions.
Is this expected as it causes the quickstart triple o to fail installation ?
Reegards Pete
hi @peteclapham - I noticed your question hasn't been answered. Are you still running into this issue? Or can I close it out?