manila manage OverQuota - no good way out
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Carlos Eduardo |
Bug Description
Hi,
I managed a share in a project without share and gigabytes quota. The share goes into state manage_error, I see an OverQuota Error in the log.
The share instance is already present at this time and the share has been renamed in the back end.
I tested this with netapp back end (dhss=true, but the code for manage_existing is in the common lib_base, should be the same for dhss=false).
I don't see a good way out of this situation now, I tried:
A) manila reset state:
- cool, I tricked the quota system
- but the export location is wrong (still shows the one I imported from, but on the back end it is already renamed; keyword junction path on netapp)
B) manila delete:
- failed with 403 Invalid share: Share status must be one of ('available', 'error', 'inactive')
C) manila force delete:
- oops this removes more than I wanted, also my back end share is gone
D) manila reset state and then manila delete:
- same as option C)
To keep my back end share and to get rid of the share in manage_error I would either need to go to the database directly or to the back end directly - both options are ugly. And may not be an option for an administrative user, who only has the API (and some info about manageable shares) to work with.
I suggest to do the quota check earlier, to fail faster before the connection to the back end share has been made.
Cheers,
Maurice
Changed in manila: | |
assignee: | nobody → Douglas Viroel (dviroel) |
Changed in manila: | |
importance: | Undecided → Medium |
Revisted see http:// eavesdrop. openstack. org/meetings/ manila/ 2020/manila. 2020-02- 20-15.00. log.html