- Manila share server deletion happens asynchronously. If deletion of
share server fails in between, share server network ports remained as
it is. So we should better delete share network ports first and then
continue share server deletion.
- It may be possible, that there are ports existing without a
corresponding manila network allocation entry in the manila db, because
port create request may have been successfully sent to neutron, but not
stored in db. So query(and delete) those from neutron after db entries
are deleted.
Closes-bug: #2067266
Change-Id: Id86dade1194494e599aea9adad06e4ca6cb119b6
(cherry picked from commit 76d032969848fa409f3b7da499cc2da3de67f6be)
Reviewed: https:/ /review. opendev. org/c/openstack /manila/ +/921292 /opendev. org/openstack/ manila/ commit/ 19622387dc54ed2 458bc514854e742 160954318c
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2024.1
commit 19622387dc54ed2 458bc514854e742 160954318c
Author: Kiran Pawar <email address hidden>
Date: Mon May 27 12:43:01 2024 +0000
Fix leak of ports on share server deletion
- Manila share server deletion happens asynchronously. If deletion of
share server fails in between, share server network ports remained as
it is. So we should better delete share network ports first and then
continue share server deletion.
- It may be possible, that there are ports existing without a
corresponding manila network allocation entry in the manila db, because
port create request may have been successfully sent to neutron, but not
stored in db. So query(and delete) those from neutron after db entries
are deleted.
Closes-bug: #2067266 e599aea9adad06e 4ca6cb119b6 09f3b7da499cc2d a3de67f6be)
Change-Id: Id86dade1194494
(cherry picked from commit 76d032969848fa4