DisassociateAddress can cause Internal Server Error

Bug #1080406 reported by Attila Fazekas on 2012-11-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Michael Still
Vish Ishaya
nova (Ubuntu)

Bug Description

I have an allocated, but not associated address and I call the address.disassociate() with boto.

query string: AWSAccessKeyId=f0d447ca4b024c36b194eafc74f7a81d&Action=DisassociateAddress&PublicIp=

For the response I got:
HTTP Status: 500
EC2 Error_Code: "500" (Not a valid EC2 error code)

The api.log log attached.

I am using the stable/folsom.

Attila Fazekas (afazekas) wrote :
tags: added: ec2
Michael Still (mikal) on 2012-11-20
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Michael Still (mikal) on 2012-11-20
tags: added: folsom-backport-potential
Michael Still (mikal) wrote :

Interestingly, euca2ools retries forever (well, as long as I could be bothered to wait) in this scenario.

Fix proposed to branch: master
Review: https://review.openstack.org/16505

Changed in nova:
assignee: nobody → Michael Still (mikalstill)
status: Triaged → In Progress

Reviewed: https://review.openstack.org/16505
Committed: http://github.com/openstack/nova/commit/c3639847011566f39a7bd08e29bab4a72847a333
Submitter: Jenkins
Branch: master

commit c3639847011566f39a7bd08e29bab4a72847a333
Author: Michael Still <email address hidden>
Date: Tue Nov 20 15:09:32 2012 +1100

    Handle instances not being found in EC2 API responses.

    Resolves bug 1080406 where InstanceNotFound was raised with None
    as the instance id.

    Change-Id: I805a9c8893f51ab22426e606ce260a04113f26e5

Changed in nova:
status: In Progress → Fix Committed

Reviewed: https://review.openstack.org/16661
Committed: http://github.com/openstack/nova/commit/6e47cc8271f84090b27e17c6bce27e909a143586
Submitter: Jenkins
Branch: stable/folsom

commit 6e47cc8271f84090b27e17c6bce27e909a143586
Author: Michael Still <email address hidden>
Date: Tue Nov 20 15:09:32 2012 +1100

    Handle instances not being found in EC2 API responses.

    Resolves bug 1080406 where InstanceNotFound was raised with None
    as the instance id.

    Change-Id: I805a9c8893f51ab22426e606ce260a04113f26e5
    (cherry picked from commit c3639847011566f39a7bd08e29bab4a72847a333)

Changed in nova (Ubuntu):
status: New → Fix Released
Changed in nova (Ubuntu Quantal):
status: New → Confirmed

Hello Attila, or anyone else affected,

Accepted nova into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nova/2012.2.1+stable-20121212-a99a802e-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in nova (Ubuntu Quantal):
status: Confirmed → Fix Committed
tags: added: verification-needed
Thierry Carrez (ttx) on 2013-01-09
Changed in nova:
milestone: none → grizzly-2
status: Fix Committed → Fix Released
Mark McLoughlin (markmc) on 2013-01-22
tags: removed: folsom-backport-potential
Launchpad Janitor (janitor) wrote :
Download full text (8.3 KiB)

This bug was fixed in the package nova - 2012.2.1+stable-20121212-a99a802e-0ubuntu1

nova (2012.2.1+stable-20121212-a99a802e-0ubuntu1) quantal-proposed; urgency=low

  * Ubuntu updates:
    - debian/control: Ensure novaclient is upgraded with nova,
      require python-keystoneclient >= 1:2.9.0. (LP: #1073289)
    - d/p/avoid_setuptools_git_dependency.patch: Refresh.
  * Dropped patches, applied upstream:
    - debian/patches/CVE-2012-5625.patch: [a99a802]
  * Resynchronize with stable/folsom (b55014ca) (LP: #1085255):
    - [a99a802] create_lvm_image allocates dirty blocks (LP: #1070539)
    - [670b388] RPC exchange name defaults to 'openstack' (LP: #1083944)
    - [3ede373] disassociate_floating_ip with multi_host=True fails
      (LP: #1074437)
    - [22d7c3b] libvirt imagecache should handle shared image storage
      (LP: #1075018)
    - [e787786] Detached and deleted RBD volumes remain associated with insance
      (LP: #1083818)
    - [9265eb0] live_migration missing migrate_data parameter in Hyper-V driver
      (LP: #1066513)
    - [3d99848] use_single_default_gateway does not function correctly
      (LP: #1075859)
    - [65a2d0a] resize does not migrate DHCP host information (LP: #1065440)
    - [102c76b] Nova backup image fails (LP: #1065053)
    - [48a3521] Fix config-file overrides for nova-dhcpbridge
    - [69663ee] Cloudpipe in Folsom: no such option: cnt_vpn_clients
      (LP: #1069573)
    - [6e47cc8] DisassociateAddress can cause Internal Server Error
      (LP: #1080406)
    - [22c3d7b] API calls to dis-associate an auto-assigned floating IP should
      return proper warning (LP: #1061499)
    - [bd11d15] libvirt: if exception raised during volume_detach, volume state
      is inconsistent (LP: #1057756)
    - [dcb59c3] admin can't describe all images in ec2 api (LP: #1070138)
    - [78de622] Incorrect Exception raised during Create server when metadata
      over 255 characters (LP: #1004007)
    - [c313de4] Fixed IP isn't released before updating DHCP host file
      (LP: #1078718)
    - [f4ab42d] Enabling Return Reservation ID with XML create server request
      returns no body (LP: #1061124)
    - [3db2a38] 'BackupCreate' should accept rotation parameter greater than or
      equal to zero (LP: #1071168)
    - [f7e5dde] libvirt reboot sometimes fails to reattach volumes
      (LP: #1073720)
    - [ff776d4] libvirt: detaching volume may fail while terminating other
      instances on the same host concurrently (LP: #1060836)
    - [85a8bc2] Used instance uuid rather than id in remove-fixed-ip
    - [42a85c0] Fix error on invalid delete_on_termination value
    - [6a17579] xenapi migrations fail w/ swap (LP: #1064083)
    - [97649b8] attach-time field for volumes is not updated for detach volume
      (LP: #1056122)
    - [8f6a718] libvirt: rebuild is not using kernel and ramdisk associated with
      the new image (LP: #1060925)
    - [fbe835f] live-migration and volume host assignement (LP: #1066887)
    - [c2a9150] typo prevents volume_tmp_dir flag from working (LP: #1071536)
    - [93efa21] Instances deleted during spawn leak network allocations
      (LP: #1068716)
    - [ebabd02] After restartin...


Changed in nova (Ubuntu Quantal):
status: Fix Committed → Fix Released
tags: added: tempest
Thierry Carrez (ttx) on 2013-04-04
Changed in nova:
milestone: grizzly-2 → 2013.1
Attila Fazekas (afazekas) wrote :

The ec2 error code is still incorrect, but at least not 500.

Dave Walker (davewalker) wrote :

Whilst looking at icehouse gate tempest logs, i noticed:
tempest.thirdparty.boto.test_ec2_network.EC2NetworkTest.test_disassociate_not_associated_floating_ip[gate,smoke] ... skipped u'Skipped until Bug: 1080406 is resolved.'

Is it still appropriate for this test to be disabled?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments