Comment 3 for bug 2023764

Here's what happening, when we run a test, the VM is spawned, and goes to ACTIVE, however, the VM get stucked in cloud-init initialization:

currently loaded modules: 8139cp 8390 9pnet 9pnet_virtio ahci drm drm_kms_helper e1000 failover fb_sys_fops hid hid_generic ip_tables isofs libahci mii ne2k_pci net_failover nls_ascii nls_iso8859_1 nls_utf8 pcnet32 qemu_fw_cfg syscopyarea sysfillrect sysimgblt ttm usbhid virtio_blk virtio_gpu virtio_input virtio_net virtio_rng virtio_scsi x_tables
Initializing random number generator... done.
Starting acpid: OK
Starting network: udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 10.100.0.3
udhcpc: lease of 10.100.0.3 obtained, lease time 43200
route: SIOCADDRT: File exists
WARN: failed: route add -net "0.0.0.0/0" gw "10.100.0.1"
OK
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 9.85. request failed
failed 2/20: up 58.99. request failed
failed 3/20: up 108.09. request failed
failed 4/20: up 157.19. request failed
failed 5/20: up 206.29. request failed

Meanwhile, the test tries to ssh, and it can't, because the ssh service on VM did not start yet.

Locally, when I ran the test manually, I was able to ping the vm, but not ssh, which proves that ssh service did not start.