Bug 1003093

Description of problem:
boto.ec2.connection.allocate_address() is supposed to return an Address object that is populated with the IP addresses allocated.  In this case, I was trying to allocate an address from an ec2 connection to Eucalyptus.  It worked fine with version python-boto 2.5.2-3.  A recent update to 2.9.9-2 seems to display broken behaviour.  

After allocating an address via allocate_address() in using 2.9.9-2, the resulting Address object has 'None' for public_ip.  It looks like the call to Eucalyptus is actually successful, but the result is not being populated to the .public_ip attribute in the Address object returned to the user.  Everything works fine with the older 2.5.2-3 version

Version-Release number of selected component (if applicable):
python-boto-2.9.9-2.el6.noarch


How reproducible:
Allocate an address via boto.ec2.connection.allocate_address()


Steps to Reproduce:
1. Create an EC2 connection to a Eucalyptus service
2. Try to allocate an address via boto.ec2.connection.allocate_address()
3. Notice that the address has None for public_ip, even though the address was successfully allocated

Actual results:
# ec2 is open connection of type boto.ec2.connection
>>> addr = ec2.allocate_address()
>>> addr
Address:None
>>> print addr.public_ip
None

euca-describe-addresses shows that this actually did successfully allocate address in Eucalyptus.  That address just isn't returned



Expected results:
# ec2 is open connection of type boto.ec2.connection
>>> addr = ec2.allocate_address()
>>> addr
Address:123.45.67.89
>>> print addr.public_ip
123.45.67.89