Bug 1483642 - nova-api throw 500 HTTP response (instead of 404) for FloatingIpNotFoundForAddress exception
Summary: nova-api throw 500 HTTP response (instead of 404) for FloatingIpNotFoundForAd...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 10.0 (Newton)
Assignee: Artom Lifshitz
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-21 14:48 UTC by Md Nadeem
Modified: 2023-09-14 04:02 UTC (History)
15 users (show)

Fixed In Version: openstack-nova-14.0.8-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-28 16:32:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 471511 0 None MERGED Catch neutronclient.NotFound on floating deletion 2020-06-26 01:14:38 UTC
Red Hat Product Errata RHBA-2017:2823 0 normal SHIPPED_LIVE openstack-nova bug fix advisory 2017-09-28 20:32:21 UTC

Description Md Nadeem 2017-08-21 14:48:16 UTC
Description of problem:

nova-api throw 500 HTTP response (instead of 404) for FloatingIpNotFoundForAddress exception.

DELETE /v2.1/os-floating-ips/f943d767-a757-4bc3-9e9d-2d7be5370cf3 HTTP/1.1" status: 500 len: 560 time: 1.6314788

Please have a look at below logs.

~~~
2017-08-15 06:57:10.307 5234 ERROR nova.api.openstack.extensions     raise exception.FloatingIpNotFoundForAddress(address=address)
2017-08-15 06:57:10.307 5234 ERROR nova.api.openstack.extensions FloatingIpNotFoundForAddress: Floating IP not found for address 10.8.241.140.
2017-08-15 06:57:10.307 5234 ERROR nova.api.openstack.extensions 
2017-08-15 06:57:10.309 5234 INFO nova.api.openstack.wsgi [req-f806b2e0-bad7-4591-809a-2a50940d2985 d1e0a9541632439288ea847aab66f30b f09d0e62c49f46a6a3b2e9911c97470a - default default] HTTP exception thrown: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
<class 'nova.exception.FloatingIpNotFoundForAddress'>
2017-08-15 06:57:10.310 5234 INFO nova.osapi_compute.wsgi.server [req-f806b2e0-bad7-4591-809a-2a50940d2985 d1e0a9541632439288ea847aab66f30b f09d0e62c49f46a6a3b2e9911c97470a - default default] 172.16.108.12 "DELETE /v2.1/os-floating-ips/f943d767-a757-4bc3-9e9d-2d7be5370cf3 HTTP/1.1" status: 500 len: 560 time: 1.6314788
~~~


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
"DELETE /v2.1/os-floating-ips/f943d767-a757-4bc3-9e9d-2d7be5370cf3 HTTP/1.1" status: 500

Expected results:
"DELETE /v2.1/os-floating-ips/f943d767-a757-4bc3-9e9d-2d7be5370cf3 HTTP/1.1" status: 404

Additional info:

Comment 2 Dan Smith 2017-08-24 16:58:26 UTC
Can you include more of the log please? Also, I assume this is with neutron, correct?

Comment 4 Dan Smith 2017-08-25 13:50:56 UTC
Looks like this needs to be backported to OSP10:

commit d99197aece6451013d1de1f08c1af16832ee0e7e
Author: Guillaume Espanel <guillaume.espanel>
Date:   Wed Dec 14 15:29:02 2016 +0100

    Catch neutronclient.NotFound on floating deletion

    In some cases, trying to delete a floating IP multiple times in a short
    delay can trigger an exception beacause the floating ip deletion
    operation is not atomic. If neutronclient's call to delete fails with a
    NotFound error, we raise a 404 error to nova's client instead of a 500.

    Change-Id: I49ea7e52073148457e794d641ed17d4ef58616f8
    Co-Authored-By: Stephen Finucane <sfinucan>
    Closes-Bug: #1649852


It's already on OSP11.

Comment 5 Dan Smith 2017-08-25 13:55:03 UTC
This was just backported to newton 13 days ago so we should get it via rebase: https://review.openstack.org/#/c/471511/

Comment 7 Dan Smith 2017-08-31 17:53:03 UTC
Added fixed-in-version

Comment 13 errata-xmlrpc 2017-09-28 16:32:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2823

Comment 14 Red Hat Bugzilla 2023-09-14 04:02:43 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.