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 <email address hidden>
Closes-Bug: #1649852
(cherry picked from commit d99197aece6451013d1de1f08c1af16832ee0e7e)
Reviewed: https:/ /review. openstack. org/471511 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f5e86d38648 5e102b7430b332e 79c6155adf6528
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit f5e86d386485e10 2b7430b332e79c6 155adf6528
Author: Guillaume Espanel <email address hidden>
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: I49ea7e52073148 457e794d641ed17 d4ef58616f8 13d1de1f08c1af1 6832ee0e7e)
Co-Authored-By: Stephen Finucane <email address hidden>
Closes-Bug: #1649852
(cherry picked from commit d99197aece64510