Deploy failed due to .ssh already existing 29/6629/1
authorMichael Chapman <woppin@gmail.com>
Thu, 14 Jan 2016 05:52:15 +0000 (16:52 +1100)
committerMichael Chapman <woppin@gmail.com>
Thu, 14 Jan 2016 05:52:15 +0000 (16:52 +1100)
In a local test, I observed virt-customize failing during ssh
key injection

Injecting ssh key to instack VM
[   0.0] Examining the guest ...
[  48.0] Setting a random seed
[  48.0] Running: mkdir /root/.ssh/
mkdir: cannot create directory '/root/.ssh/': File exists
virt-customize: mkdir /root/.ssh/: command exited with an error

Adding -p should prevent this from happening.

Change-Id: If8f085cba3083ccf3d5e8f648a9830f142ea53d9

ci/deploy.sh

index 05df640..0ae7bf8 100755 (executable)
@@ -511,7 +511,7 @@ function setup_instack_vm {
   # if the VM is not running update the authkeys and start it
   if ! virsh list | grep instack > /dev/null; then
     echo "Injecting ssh key to instack VM"
-    virt-customize -c qemu:///system -d instack --run-command "mkdir /root/.ssh/" \
+    virt-customize -c qemu:///system -d instack --run-command "mkdir -p /root/.ssh/" \
         --upload ~/.ssh/id_rsa.pub:/root/.ssh/authorized_keys \
         --run-command "chmod 600 /root/.ssh/authorized_keys && restorecon /root/.ssh/authorized_keys" \
         --run-command "cp /root/.ssh/authorized_keys /home/stack/.ssh/" \