76d0329698
- 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
11 lines
538 B
YAML
11 lines
538 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Share server deletion happens asynchronously and failure during this delete
|
|
results in leakage of neutron ports. This is fixed in two steps, first by
|
|
trying to delete ports before share server deletion. Second, after ports
|
|
from Manila db entries are deleted, query is made to neutron to get ports
|
|
which are allocated for share server and missing in db. And then try to
|
|
delete those ports. For more details please check
|
|
Launchpad `bug 2067266 <https://bugs.launchpad.net/manila/+bug/2067266>`_
|