IPA ramdisk may offer SSH, causing race

[Julia Kreger]

IPA ramdisk can offer SSH, which will allow the test to prematurely proceed prior to the VMs deployment being completed.

This was observed in CI with the DHCP test sequence.

changed: [testvm1] => {"changed": true, "cmd": "ssh-keyscan \"192.168.122.2\" >> \"/home/jenkins/.ssh/known_hosts\"", "delta": "0:00:00.206401", "end": "2016-03-20 13:09:53.739021", "invocation": {"module_args": {"_raw_params": "ssh-keyscan \"192.168.122.2\" >> \"/home/jenkins/.ssh/known_hosts\"", "_uses_shell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "module_name": "command"}, "rc": 0, "start": "2016-03-20 13:09:53.532620", "stderr": "# 192.168.122.2 SSH-2.0-dropbear_2012.55\n# 192.168.122.2 SSH-2.0-dropbear_2012.55\nno hostkey alg", "stdout": "", "stdout_lines": [], "warnings": []}
changed: [testvm3] => {"changed": true, "cmd": "ssh-keyscan \"192.168.122.4\" >> \"/home/jenkins/.ssh/known_hosts\"", "delta": "0:00:00.222124", "end": "2016-03-20 13:09:53.767244", "invocation": {"module_args": {"_raw_params": "ssh-keyscan \"192.168.122.4\" >> \"/home/jenkins/.ssh/known_hosts\"", "_uses_shell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "module_name": "command"}, "rc": 0, "start": "2016-03-20 13:09:53.545120", "stderr": "# 192.168.122.4 SSH-2.0-dropbear_2012.55\nno hostkey alg\r\n# 192.168.122.4 SSH-2.0-dropbear_2012.55", "stdout": "", "stdout_lines": [], "warnings": []}
changed: [testvm2] => {"changed": true, "cmd": "ssh-keyscan \"192.168.122.3\" >> \"/home/jenkins/.ssh/known_hosts\"", "delta": "0:00:01.437911", "end": "2016-03-20 13:09:54.982942", "invocation": {"module_args": {"_raw_params": "ssh-keyscan \"192.168.122.3\" >> \"/home/jenkins/.ssh/known_hosts\"", "_uses_shell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "module_name": "command"}, "rc": 0, "start": "2016-03-20 13:09:53.545031", "stderr": "# 192.168.122.3 SSH-2.0-OpenSSH_6.6p1-hpn14v4\nno hostkey alg\r\n# 192.168.122.3 SSH-2.0-OpenSSH_6.6p1-hpn14v4", "stdout": "", "stdout_lines": [], "warnings": []}

Example above of the resulting plays where 192.168.122.3 is offering OpenSSH instead of dropbear, meaning Cirros is not yet deployed.

We need to re-structure the waiting and possibly verify active state in the long run.

[Stephane Miller (stephaneeee)]

Workaround posted in https://review.openstack.org/#/c/295040/. This bug should remain open so we can develop a better solution.