Comment 21 for bug 566792

OK. I think I've figured out what is causing this.
in 100% of the failed instances that I'm seeing today, the instance has its public ip identical to its private ip.

Ie, the following is euca-describe-instances output of a failed instance:
INSTANCE i-2F1A0573 emi-E58B1525 172.19.1.48 172.19.1.48 running uectest-k0 0 m1.small 2010-05-20T15:34:28.275Z UEC-TEST1 eki-2B241A2B

And this is from a successful instance:
INSTANCE i-37A30725 emi-E58B1525 10.55.55.187 172.19.1.34 running uectest-k0 0 m1.small 2010-05-20T15:34:06.874Z UEC-TEST1 eki-2B241A2B

Note, these instances were not launched with '--addressing private'.

$ euca-describe-addreses | sort
ADDRESS 10.55.55.100 i-4A34090E (eucalyptus)
ADDRESS 10.55.55.101 available (nobody)
ADDRESS 10.55.55.102 available (eucalyptus)
...
ADDRESS 10.55.55.238 nobody
ADDRESS 10.55.55.239 nobody
ADDRESS 10.55.55.240 nobody
$ euca-describe-addresses | grep nobody | wc -l
24
$ euca-describe-addresses | wc -l
141

It seems there should have been addresses available, euca-describe-availability-zones only shows 32 instances max.

# on the cloud-controller
cc-host$ cat /etc/eucalyptus/eucalyptus.local.conf
VNET_MODE="MANAGED-NOVLAN"
VNET_SUBNET="172.19.0.0"
VNET_NETMASK="256.255.0.0"
VNET_DNS="10.55.55.1"
VNET_ADDRSPERNET="32"
VNET_PUBLICIPS="10.55.55.100-10.55.55.240"
VNET_CLOUDIP="10.55.55.2"

The testcases (lp:~uec-testing-scripts-dev/uec-testing-scripts/trunk/) basically keep firing off instances 1 by 1 with euca-run-instances as long as 'euca-describe-availability-zones verbose' reports that there is space. Note, instances are ran *without* '--addressing private', but appear to be getting private addressing.