Description
===========
Several times today I have tried to use quickstart.sh and each time it has failed because the script is unable to pick up the IP from the undercloud VM. It looks as though the VM has crashed, because the KVM process is stuck at 100% and the virsh console is not responsive - it connects and shows nothing when I press enter.
Steps to reproduce
==================
bash quickstart.sh --install-deps
export VIRTHOST=<virthost IP>
bash quickstart.sh -R queens $VIRTHOST
Expected result
===============
undercloud VM starts normally and the rest of the script proceeds.
Actual result
=============
The script cannot capture the undercloud VM IP, so it stops:
TASK [setup/undercloud : Start undercloud vm] ********************************************************************************************************************************************************
task path: /home/stack/.quickstart/tripleo-quickstart/roles/libvirt/setup/undercloud/tasks/main.yml:328
Wednesday 11 April 2018 17:38:31 +0100 (0:00:00.042) 0:12:13.584 *******
changed: [10.188.2.120] => {"changed": true, "failed": false, "msg": 0}
TASK [setup/undercloud : Get undercloud vm ip address] ***********************************************************************************************************************************************
task path: /home/stack/.quickstart/tripleo-quickstart/roles/libvirt/setup/undercloud/tasks/main.yml:341
Wednesday 11 April 2018 17:38:33 +0100 (0:00:01.901) 0:12:15.485 *******
FAILED - RETRYING: Get undercloud vm ip address (20 retries left).
FAILED - RETRYING: Get undercloud vm ip address (19 retries left).
FAILED - RETRYING: Get undercloud vm ip address (18 retries left).
FAILED - RETRYING: Get undercloud vm ip address (17 retries left).
FAILED - RETRYING: Get undercloud vm ip address (16 retries left).
FAILED - RETRYING: Get undercloud vm ip address (15 retries left).
FAILED - RETRYING: Get undercloud vm ip address (14 retries left).
FAILED - RETRYING: Get undercloud vm ip address (13 retries left).
FAILED - RETRYING: Get undercloud vm ip address (12 retries left).
FAILED - RETRYING: Get undercloud vm ip address (11 retries left).
FAILED - RETRYING: Get undercloud vm ip address (10 retries left).
FAILED - RETRYING: Get undercloud vm ip address (9 retries left).
FAILED - RETRYING: Get undercloud vm ip address (8 retries left).
FAILED - RETRYING: Get undercloud vm ip address (7 retries left).
FAILED - RETRYING: Get undercloud vm ip address (6 retries left).
FAILED - RETRYING: Get undercloud vm ip address (5 retries left).
FAILED - RETRYING: Get undercloud vm ip address (4 retries left).
FAILED - RETRYING: Get undercloud vm ip address (3 retries left).
FAILED - RETRYING: Get undercloud vm ip address (2 retries left).
FAILED - RETRYING: Get undercloud vm ip address (1 retries left).
fatal: [10.188.2.120]: FAILED! => {"attempts": 20, "changed": true, "failed": true, "msg": "non-zero return code", "rc": 1, "stderr": "Connection to 10.188.2.120 closed.\r\n", "stdout": "undercloud ip is not available\r\n", "stdout_lines": ["undercloud ip is not available"]}
PLAY RECAP *******************************************************************************************************************************************************************************************
10.188.2.120 : ok=140 changed=58 unreachable=0 failed=1
localhost : ok=11 changed=4 unreachable=0 failed=0
I saw the same result with Pike.
Environment
===========
CentOS 7.4
you're probably having issues with RDO cloud, don't you?