scheduler chooses a storagepool without enough capacity
Bug #1621470 reported by
liucheng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
Two storagepools are configured, and the free capacity of the two pools is different, for example one has 200GB left, the other has 300.5GB left. When I create a volume with 300GB, the later pool will be chosen. The problem is before driver report the free capacity of each pool, I create a volume with 1GB, the later pool with be chosen, but there is no
enough capacity for the new volume.
Changed in cinder: | |
assignee: | nobody → Justin A Wilson (justin-wilson) |
To post a comment you must log in.
are you using thick and thin volumes?