Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857716 Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/f9ccb4c48627a200ef27dde60b01bccdccac4e45 Submitter: "Zuul (22348)" Branch: master
commit f9ccb4c48627a200ef27dde60b01bccdccac4e45 Author: Fernando Royo <[email protected]> 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 Change-Id: I91b29add2a5d2ca3d4eff4b8d6a88be16c42be51 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1990129 Title: [ovn-octavia-provider] Avoid LB in ERROR status on delete due to LR/LS not found Status in neutron: Fix Released Bug description: The LB delete operation a single transaccion will delete the LB reference from all LS and LR, and also the deletion of the LB itself. As it is in an atomic transaction, if any operation fails, the whole operation will report a LB ERROR status. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1990129/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
