Capacity filter should check free space if total space is unknown
Bug #1490364 reported by
Clinton Knight
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Clinton Knight |
Bug Description
The Manila capacity filter accepts values of 'unknown' for both total and free space in a pool. If free space is unknown, then the scheduler always allows a create (as it should). But the scheduler also always allows a create if total space is unknown, even if free space is known; in this case, the filter should compare the request against the available free space before allowing the create.
Changed in manila: | |
status: | Triaged → In Progress |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | liberty-rc1 → 1.0.0 |
To post a comment you must log in.
Is there any driver that reports 'unknown' for total but an actual number for free? I didn't think that is a realistic case. If a driver knows free, it should also know total. If a driver reports 'unknown' total but an actual number for free, I think that is an implementation error that we should not encourage.