yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1224251

Title:
  disassociate_address on unassociated address does not return proper
  EC2 response

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  disassociate_address does not return the appropriate EC2 response when
  disassociating an unassociated address. Despite this seeming failure,
  EC2 will respond success.

  EC2 will return as such:
  <DisassociateAddressResponse xmlns="http://EC2.amazonaws.com/doc/2012-08-15/";>
      <requestId>aabbccdd-0146-4952-bdbe-710e4fee8387</requestId>
      <return>true</return>
  </DisassociateAddressResponse>

  yet, when the EC2 api encounters this scenario, it responds with a 400:
  ERROR:boto:400 Bad Request
  ERROR:boto:<?xml version="1.0"?>
  <Response><Errors><Error><Code>InvalidInstanceID.NotFound</Code><Message>Instance None could not be found.</Message></Error></Errors><RequestID>req-7a9b4d03-b9f5-4243-95d8-f1ccab180631</RequestID></Response>

  The EC2 api should evaluate whether it receives an instance_id from:
  instance_id = self.network_api.get_instance_id_by_floating_address(context, public_ip)

  and, if so, then continue attempting to disassociate. Else, bail out
  early and return successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1224251/+subscriptions