Handle properly ObjectNotFound while deleting network from DHCP agent
In case when 2 neutron servers are trying to remove network from the
same DHCP agent it may happend that one of them will not be able
to find binding object anymore thus deletion of that binding object
will raise ObjectNotFound exception.
This patch adds proper handling of such case to not raise ugly
stacktrace in neutron logs.
Closes-Bug: #1970759
Change-Id: I67d516c4583aa0c20416114b92a6d69ece5b970c
(cherry picked from commit 8df2f69b6f93fd964cc96efb42d085063b90a8e6)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/840481 /opendev. org/openstack/ neutron/ commit/ 97efa2a5ad5be4d 5aa13441ae7ef83 de6286a211
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/xena
commit 97efa2a5ad5be4d 5aa13441ae7ef83 de6286a211
Author: Slawek Kaplonski <email address hidden>
Date: Thu Apr 28 16:51:25 2022 +0200
Handle properly ObjectNotFound while deleting network from DHCP agent
In case when 2 neutron servers are trying to remove network from the
same DHCP agent it may happend that one of them will not be able
to find binding object anymore thus deletion of that binding object
will raise ObjectNotFound exception.
This patch adds proper handling of such case to not raise ugly
stacktrace in neutron logs.
Closes-Bug: #1970759 c20416114b92a6d 69ece5b970c 64cc96efb42d085 063b90a8e6)
Change-Id: I67d516c4583aa0
(cherry picked from commit 8df2f69b6f93fd9