Manila allows share type deletion despite quota allocations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Goutham Pacha Ravi |
Bug Description
Manila seems allows share type deletions when there are still per project quota allocations.
I found this when purging our Manila DB ("manila-manage db purge") and ran into a situation where the foreign key constraint on project_
Apart from direct DB manipulation there seems to be no way to get out of this situation.
I think Manila should do one of the following:
a) make "manila type-delete" fail if that violates a foreign key constraint (in this case if there are entries in project_
b) offer a "--force" option to "manila quota-delete" to ignore non-existing types.
My preference would be a), but b) is probably easier coding-wise (and would at least avoid that operators need to directly change the database).
tags: | added: db |
tags: | added: quotas |
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
milestone: | none → stein-3 |
tags: | added: backport-potential |
Changed in manila: | |
milestone: | stein-3 → stein-rc1 |
Hey Arne,
Do you think we should rather cleanup quota allocations when you delete a share type? I don't think we care about quotas if the type cannot be used.