+++ This bug was initially created as a clone of Bug #1789746 +++
When using Kuryr SDN the number of resources created on the
OpenStack side is way larger than for the OpenShift SDN case.
For this reason, as there is no specific order for the resources
to be deleted, the chances of the deletion of one resource (e.g.,
a network) being blocked by the deletion of another (e.g. a port
on that network) are higher, thus needing more retries or the
destroy command times out
Verified in 4.3.0-0.nightly-2020-02-11-113855 on top of OSP 13 2020-01-15.3.
Cluster deletion works, all the resources are deleted and no time-out is reached.
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.