Bug 1731174

Summary: Neutron cleanup fails sometimes due to 404 response
Product: Red Hat OpenStack Reporter: Slawek Kaplonski <skaplons>
Component: openstack-tempestAssignee: Slawek Kaplonski <skaplons>
Status: CLOSED ERRATA QA Contact: Martin Kopec <mkopec>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: apevec, lhh, mkopec, slinaber, udesale
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tempest-19.0.0-5.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1731173 Environment:
Last Closed: 2019-11-06 16:53:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1731173, 1731176    
Bug Blocks:    

Description Slawek Kaplonski 2019-07-18 14:15:33 UTC
+++ This bug was initially created as a clone of Bug #1731173 +++

It may happen that cleanup of neutron resources (e.g. network, subnet, port or router) may fail because DELETE request will be processed for very long time by neutron and retried request will got response 404.

To avoid such failures cleanup should handle 404 response as something "normal" and not fail then.

Comment 3 Martin Kopec 2019-10-06 09:29:49 UTC
The fix is present in the Fixed in version package.

Exact verification of this BZ is hard because as it's said here, it was happening only sometimes. However, adding a logic which ignores NotFound errors on DELETE requests (if the resource is not there at the time of its deletion, it can be considered as deleted successfully) should logically solve the described issue. I reviewed the code and checked upstream comments to the issue as well and it seems the change is done on all required places.
So, I'm moving this to VERIFIED.

Comment 5 errata-xmlrpc 2019-11-06 16:53:25 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.