Disk resource consumption is inconsistent between scheduler and resource tracker
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned |
Bug Description
The way scheduler consumes disk resources in host state is inconsistent with RT's way in compute service.
The scheduler consumes "free_disk_mb" in its host state.
https:/
It comes from the min value of "free_disk_gb" and "disk_available
https:/
But compute node changes "local_gb_used" instead in consuming resources from a request. https:/
There is a inconsistent gap(confirmed) of compute node state between scheduler and resource tracker, but somehow the compute node will be updated by virt driver to the consistent status after maybe 10 seconds.
Changed in nova: | |
assignee: | nobody → Yingxin (cyx1231st) |
status: | New → In Progress |
Changed in nova: | |
status: | In Progress → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
tags: | added: scheduler |
Changed in nova: | |
assignee: | nobody → Yingxin (cyx1231st) |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | Yingxin (cyx1231st) → nobody |
Change to Medium because it is a prerequisite of future schedulers such as resource-provider scheduler and shared-state scheduler.