netapp: shares without backing vserver cannot be deleted without force option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
kiran pawar |
Bug Description
Hi,
I'm on Xena with NetApp DHSS=true.
Due to whatever reasons I have a share server in error (e.g. CIFS with wrong options) and a related share also in error state.
The backing vserver has not been created (or has been rolled back), but the database objects share server and share (and share instance) are still present.
I expect that I can delete the share, but actually it ends up in error_deleting.
Only mitigation option now is doing force-delete, but that is something I don't hand out to my end users to avoid orphans on the NetApp backend.
I see the following trace https:/
The behaviour changed with https:/
Because the vserver is not present, it can not build the client.
I think _get_vserver needs to raise exception.
Do you think this makes sense?
Best regards,
Maurice
tags: | added: netapp |
Changed in manila: | |
assignee: | nobody → Andre Luiz Beltrami Rocha (andrebeltrami) |
milestone: | none → zed-1 |
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
milestone: | zed-1 → zed-2 |
Changed in manila: | |
milestone: | zed-2 → zed-3 |
Changed in manila: | |
assignee: | Andre Luiz Beltrami Rocha (andrebeltrami) → kiran pawar (kpdev) |
Changed in manila: | |
milestone: | zed-3 → zed-rc1 |
Changed in manila: | |
milestone: | zed-rc1 → antelope-1 |
Changed in manila: | |
milestone: | antelope-1 → antelope-2 |
Changed in manila: | |
milestone: | antelope-2 → antelope-3 |
Additional information is at https:/ /meetings. opendev. org/meetings/ manila/ 2022/manila. 2022-03- 17-15.00. log.html