Fix leak of Manila ports on share server deletion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
kiran pawar |
Bug Description
There are two scenarios we observed
1. if we want to delete a share server, we should double check if there are ports belonging to the share server. 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 the response, the created port could not be stored in manila due to unreachable db (e.g. during manila-share deployment when proxysql sidecar gets terminated)
2. Manila share server deletion happens asynchronously. If deletion of share server fails in between, share server network ports remained as it is. This is leak. So we should better delete share network ports first and then continue share server deletion.
Changed in manila: | |
assignee: | nobody → kiran pawar (kpdev) |
Changed in manila: | |
milestone: | none → dalmatian-2 |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/openstack /manila/ +/920513
Review: https:/