Avoid LB ERROR status on delete when LS/LR are already deleted
The delete operation of an LB lists all references to it (LS and
LR) and in a single transaction deletes them together with the
LB itself. If any of those deletions raise a RowNotFound exception,
the execution will report ERROR status.
This patch will reduce those situations, rechecking the command
that triggers the RowNotFound exception and passing in case a LS
or a LR was the culprit, deleting finally the LB and reporting as
a DELETED status. In other case, the exception is raised and
finally the LB will be reported as ERROR status.
Closes-Bug:#1990129
(manually cherry picked from commit f9ccb4c48627a200ef27dde60b01bccdccac4e45)
Reviewed: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/859534 /opendev. org/openstack/ ovn-octavia- provider/ commit/ c1976cf761a25a3 e28ed28b22422ad 8b80055a18
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/ussuri
commit c1976cf761a25a3 e28ed28b22422ad 8b80055a18
Author: Fernando Royo <email address hidden>
Date: Wed Sep 14 15:52:43 2022 +0200
Avoid LB ERROR status on delete when LS/LR are already deleted
The delete operation of an LB lists all references to it (LS and
LR) and in a single transaction deletes them together with the
LB itself. If any of those deletions raise a RowNotFound exception,
the execution will report ERROR status.
This patch will reduce those situations, rechecking the command
that triggers the RowNotFound exception and passing in case a LS
or a LR was the culprit, deleting finally the LB and reporting as
a DELETED status. In other case, the exception is raised and
finally the LB will be reported as ERROR status.
Closes- Bug:#1990129
(manually cherry picked from commit f9ccb4c48627a20 0ef27dde60b01bc cdccac4e45)
Depends-On: https:/ /review. opendev. org/c/openstack /ovn-octavia- provider/ +/859625
Change-Id: I91b29add2a5d2c a3d4eff4b8d6a88 be16c42be51 0ef27dde60b01bc cdccac4e45)
(cherry picked from commit f9ccb4c48627a20