get-pools doesn't reflect capacity change made by consume_from_volume

Bug #1748696 reported by TommyLike on 2018-02-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When creating volume, we will decrease pool's free_capacity_gb, but get-pools' API will not reflect this change, follow this reproduce procedure:
1. cinder get-pools -detail
2. cinder create {size}
3. wait for volume successfully scheduled and make sure the scheduler's backend states have not been updated by backend.
4. cinder-get-pools --detail
5. "free_capacity_gb" keep unchanged.

TommyLike (hu-husheng) on 2018-02-11
Changed in cinder:
assignee: nobody → TommyLike (hu-husheng)
TommyLike (hu-husheng) wrote :

Havn't tested this in Manila environment, but it may also exist in Manila as Cinder and Manila share most of the same codes here.

Fix proposed to branch: master

Changed in cinder:
status: New → In Progress
Tom Barron (tpb) wrote :

From xyang:

<xyang> tbarron, bswartz: I took a look of the get pools bug. I don’t think we need to rush to get this in. It’s still been debated in Cinder. It does look like Manila has the same issue by inspecting the code. This is not related to oversubscription. It is a general capabilities reporting problem. The root case is capabilities reporting is periodic. So there is a period when the data is stale. In this
<xyang> case a volume is created in the period between two capabilities reporting from backends so the pools stats are not updated yet.
<xyang> This fix let the scheduler update the capacities after create volume process is done in scheduler, but before there is a response from the backend. So this update is not completely accurate. If volume create is successful, it is accurate. If volume create fails in the backend, this is not accurate. When capabilities reporting happens for the next time, pools stats will be corrected. So this fix
<xyang> temporarily updates the pools stats until the next capabilities reporting from the backend.

junboli (junboli) on 2018-05-17
Changed in manila:
assignee: nobody → junboli (junboli)
Changed in manila:
status: New → In Progress
importance: Undecided → Medium
junboli (junboli) on 2018-09-13
Changed in manila:
assignee: junboli (junboli) → nobody
Jason Grosso (jgrosso) on 2019-09-26
Changed in manila:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers