NetApp: thin provisioning is not enabled unless the extra spec is defined in share types
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Triaged
|
Medium
|
Felipe Rodrigues |
Bug Description
Description:
When a share is created with the sare type without the thin_provisioning spec, Manila ENABLES thin provisioning automatically.
https:/
https:/
On the other hand, When NetApp driver determines the options used to creates a new share in the backend storage, it considers thin provisioning is DISABLED if the spec is not defined in the share type.
https:/
https:/
https:/
Because of this inconsistency, when a share requires overcommit, the capacity filter can select the backend(because thin provisioning is enabled) while the backend storage doesn't allow creating new shares(because thin provisioning is disabled)
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to reproduce:
1. Create a share type without thin_provisioning extra spec
2. Create shares to allocate all capacity
3. Create a new share
Expected result:
Share creation should succeed
Actual results:
Share creation fails because manila-scheduler can't create the new share in the backend
See additional discussions at https:/ /meetings. opendev. org/meetings/ manila/ 2022/manila. 2022-05- 12-15.00. log.html