commit 440e9596520ae7bda5ce3c4773ad48805da6cba5
Author: Elvira García <email address hidden>
Date: Fri May 19 20:30:47 2023 +0200
[ovn] Avoid unwanted ACL_NOT_FOUND error when deleting log objects
There is the possibility that db_remove raises an error if an ACL was
deleted on parallel for other reasons while deleting a log object. On a
normal situation, this command would remove the no-longer-needed
'log-related' property, but since the ACL is no longer there, it will
raise an error. For this case, it is not problematic to have an ACL
deleted mid-operation, so it should not raise any error.
Related-Bug: #2019887
Signed-off-by: Elvira García <email address hidden>
Change-Id: I154393529134b5861e0ef0283257ef964fe057fd
(cherry picked from commit e0a2427a2f701adae14cd8196e3c2f064416d044)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/883720 /opendev. org/openstack/ neutron/ commit/ 440e9596520ae7b da5ce3c4773ad48 805da6cba5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/xena
commit 440e9596520ae7b da5ce3c4773ad48 805da6cba5
Author: Elvira García <email address hidden>
Date: Fri May 19 20:30:47 2023 +0200
[ovn] Avoid unwanted ACL_NOT_FOUND error when deleting log objects
There is the possibility that db_remove raises an error if an ACL was
deleted on parallel for other reasons while deleting a log object. On a
normal situation, this command would remove the no-longer-needed
'log-related' property, but since the ACL is no longer there, it will
raise an error. For this case, it is not problematic to have an ACL
deleted mid-operation, so it should not raise any error.
Related-Bug: #2019887
Signed-off-by: Elvira García <email address hidden> 861e0ef0283257e f964fe057fd ae14cd8196e3c2f 064416d044)
Change-Id: I154393529134b5
(cherry picked from commit e0a2427a2f701ad