Comment 5 for bug 1870319

Getting back to this. I was doing some research about return codes in such cases and unfortunately it seems for me that there are no strict guidelines for that.
I checked how e.g. Octavia's API with cascade loadbalancer deletion works and it returns 204 always but their API is asynchronous so user needs to periodically check if all is already gone or not.

AFAIU In case of Neutron API is synchronous when speaking about resources in DB so would need to return something after network is actually deleted. And I think that the best solution would be to return code according to the success or failure of deletion of network resource as this is what is requested. So e.g. if some ports were deleted, others not and finally network wasn't deleted due to those leftover ports, I think we should return e.g. 409 Conflict in such case as network couldn't be deleted really.
If You have other ideas, I'm open for the proposals :)