EC2 API AssociateAddress not compliant on addresses already in use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
John Tran |
Bug Description
In case a floating ip address is associated with a new instance via EC2 API call (AssociateAddress) and the address was already in use by another instance an exception is raised in the EC2 API and a error is returned to the caller of the API.
According to EC2 API Documentation this should not be the case and the address should be assigned to the new instance:
"""
For EC2 addresses: This action associates an Elastic IP address with an instance (not running in a VPC). If the IP address is currently assigned to another instance, the IP address is assigned to the new instance. For more information about EC2 Elastic IP addresses, go to Instance Addressing in the Amazon Elastic Compute Cloud User Guide.
"""
VERSION INFO:
Essex ubuntu package nova-api 2012.1-0ubuntu2
TRACES:
(nova.api.ec2): 2012-05-26 13:17:57,379 ERROR Unexpected error raised: Remote error: FloatingIpAssoc
[u'Traceback (most recent call last):\n', u' File "/usr/lib/
Traceback (most recent call last):
File "/usr/lib/
result = api_request.
File "/usr/lib/
result = method(context, **args)
File "/usr/lib/
address=
File "/usr/lib/
return func(self, context, target, *args, **kwargs)
File "/usr/lib/
floating_
File "/usr/lib/
'affect_
File "/usr/lib/
return _get_impl(
File "/usr/lib/
return rpc_amqp.
File "/usr/lib/
rv = list(rv)
File "/usr/lib/
raise result
RemoteError: Remote error: FloatingIpAssoc
tags: | added: ec2 |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | nobody → John Tran (jtran) |
Changed in nova: | |
milestone: | none → folsom-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-rc1 → 2012.2 |
https:/ /review. openstack. org/#/c/ 9566/