Comment 2 for bug 1802971

From both the logs, after ssh into cirros image, it tries to find the instance-id of the data source but it failed:
checking http://169.254.169.254/2009-04-04/instance-id
2018-11-12 17:40:46 | failed 1/20: up 188.34. request failed
2018-11-12 17:40:46 | failed 2/20: up 190.71. request failed
2018-11-12 17:40:46 | failed 3/20: up 192.88. request failed
2018-11-12 17:40:46 | failed 4/20: up 195.14. request failed
2018-11-12 17:40:46 | failed 5/20: up 197.43. request failed
2018-11-12 17:40:46 | failed 6/20: up 199.58. request failed
2018-11-12 17:40:46 | failed 7/20: up 201.87. request failed
2018-11-12 17:40:46 | failed 8/20: up 203.99. request failed
2018-11-12 17:40:46 | failed 9/20: up 206.25. request failed
2018-11-12 17:40:46 | failed 10/20: up 208.38. request failed
2018-11-12 17:40:46 | failed 11/20: up 210.69. request failed
2018-11-12 17:40:46 | failed 12/20: up 212.93. request failed
2018-11-12 17:40:46 | failed 13/20: up 215.10. request failed
2018-11-12 17:40:46 | failed 14/20: up 217.41. request failed
2018-11-12 17:40:46 | failed 15/20: up 219.55. request failed
2018-11-12 17:40:46 | failed 16/20: up 221.85. request failed
2018-11-12 17:40:46 | failed 17/20: up 223.98. request failed
2018-11-12 17:40:46 | failed 18/20: up 226.26. request failed
2018-11-12 17:40:46 | failed 19/20: up 228.43. request failed
2018-11-12 17:40:46 | failed 20/20: up 230.67. request failed
2018-11-12 17:40:46 | failed to read iid from metadata. tried 20
2018-11-12 17:40:46 | no results found for mode=net. up 232.92. searched: nocloud configdrive ec2
2018-11-12 17:40:46 | failed to get instance-id of datasource
2018-11-12 17:40:46 | Top of dropbear init script
2018-11-12 17:40:46 | Starting dropbear sshd: failed to get instance-id of datasource

Which is leading to ssh timedout.