Comment 1 for bug 1522824

Revision history for this message
Oleg Bondarev (obondarev) wrote :

Instance console logs shows that there was a problem with fetching metadata:

2015-12-04 01:17:12.854 | checking http://169.254.169.254/2009-04-04/instance-id
2015-12-04 01:17:12.854 | failed 1/20: up 186.40. request failed
2015-12-04 01:17:12.855 | failed 2/20: up 188.70. request failed
2015-12-04 01:17:12.855 | failed 3/20: up 190.82. request failed
2015-12-04 01:17:12.855 | failed 4/20: up 192.95. request failed
2015-12-04 01:17:12.855 | failed 5/20: up 195.09. request failed
2015-12-04 01:17:12.855 | failed 6/20: up 197.36. request failed
2015-12-04 01:17:12.855 | failed 7/20: up 199.50. request failed
2015-12-04 01:17:12.855 | failed 8/20: up 201.62. request failed
2015-12-04 01:17:12.856 | failed 9/20: up 203.74. request failed
2015-12-04 01:17:12.856 | failed 10/20: up 205.88. request failed
2015-12-04 01:17:12.856 | failed 11/20: up 208.15. request failed
2015-12-04 01:17:12.856 | failed 12/20: up 210.28. request failed
2015-12-04 01:17:12.856 | failed 13/20: up 212.42. request failed
2015-12-04 01:17:12.856 | failed 14/20: up 214.54. request failed
2015-12-04 01:17:12.856 | failed 15/20: up 216.66. request failed
2015-12-04 01:17:12.857 | failed 16/20: up 218.94. request failed
2015-12-04 01:17:12.857 | failed 17/20: up 221.07. request failed
2015-12-04 01:17:12.857 | failed 18/20: up 223.21. request failed
2015-12-04 01:17:12.857 | failed 19/20: up 225.34. request failed
2015-12-04 01:17:12.857 | failed 20/20: up 227.52. request failed
2015-12-04 01:17:12.858 | failed to read iid from metadata. tried 20