Commit 56463a5e authored by Michael Chapman's avatar Michael Chapman

Deploy failed due to .ssh already existing

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
parent b08e3323
......@@ -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/" \
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment