# Revision history [back]

Not sure if it is relevant, but I encountered errors with launching Ubuntu images with an m1.tiny. The issue was a lack of available space on the flavor's disk, which is now a default value of 1G. I increased the disk size by editing the flavor and the problem went away.

Not sure if it is relevant, but I encountered errors with launching Ubuntu images with an m1.tiny. The issue was a lack of available space on the flavor's disk, which is now a default value of 1G. 1G in Icehouse. I increased the disk size by editing the flavor and the problem went away.

Note: Editing my 'answer' because the first assumption about flavor size was incorrect. I'll leave the text of that below for completeness.

The spot where your instance stops is clearly involving cloud-init. I've had problems before with instances not being able to contact the metadata server that should be running on 169.254.169.254. Try pinging 169.254.169.254 from the controller node and see if you get a response. Try booting a cirros image and see if you can ping that address as well from the instance.

ubuntu@stackmonkey-va:/var/www/xoviova$ping 169.254.169.254 PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data. 64 bytes from 169.254.169.254: icmp_req=1 ttl=64 time=0.244 ms 64 bytes from 169.254.169.254: icmp_req=2 ttl=64 time=0.257 ms  Original answer was as follows: Not sure if it is relevant, but I encountered errors with launching Ubuntu images with an m1.tiny. The issue was a lack of available space on the flavor's disk, which is now a default value of 1G in Icehouse. I increased the disk size by editing the flavor and the problem went away. Note: Editing my 'answer' because the first assumption about flavor size was incorrect. I'll leave the text of that below for completeness.completeness as it is relevant to the "won't boot" part of the question. The spot where your instance stops is clearly involving cloud-init. I've had problems before with instances not being able to contact the metadata server that should be running on 169.254.169.254. Try pinging 169.254.169.254 from the controller node and see if you get a response. Try booting a cirros image and see if you can ping that address as well from the instance. ubuntu@stackmonkey-va:/var/www/xoviova$ ping 169.254.169.254
PING 169.254.169.254 (169.254.169.254) 56(84) bytes of data.
64 bytes from 169.254.169.254: icmp_req=1 ttl=64 time=0.244 ms
64 bytes from 169.254.169.254: icmp_req=2 ttl=64 time=0.257 ms