Host manager uses a different value for free disk than compute manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
moorryan |
Bug Description
There are two metrics in the system which describe how much disc space is
available on a compute host (both stored in compute_nodes):
free_gb is calculated from the maximum available space in the filesystem
minus the amount of disc space defined by the instance type of each instance
on the host.
disk_available_
Under normal conditions disk_available_
However where an instance exists in the DB but not on the host, which can happen for some Error conditions, then free_gb may be less that disk_available_
Currently the scheduler (host manager) builds its view of the amount of free disk space from disk_least_
https:/
The compute manager resource tracker on the other hand always uses free_diks_gb when deciding if an instance fits or not.
https:/
In the case where disk_least_
Clearly using two different metrics in this way is not healthy.
At a minimum the scheduler should use the minimum of the two values (since the "missing" VM may come back its not safe to just ignore it).
Would probably be better if the compute manager also did the same thing.
Changed in nova: | |
assignee: | nobody → moorryan (moorryan) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Medium |
description: | updated |
Changed in nova: | |
milestone: | none → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/57708
Review: https:/