** Also affects: compute-hyperv
Importance: Undecided
Status: New
** Changed in: compute-hyperv
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1717892
Title:
hyperv: Driver does not report disk_available_least
Status in compute-hyperv:
In Progress
Status in OpenStack Compute (nova):
In Progress
Bug description:
Description
===========
The Hyper-V driver does not report the disk_available_least field.
Reporting the mentioned field can help mitigate the scheduling issue
regarding hosts using the same shared storage.
Steps to reproduce
==================
Have a compute node having X GB total storage (reported as local_gb),
out of which, just 1 GB is actually free (unreported). The compute
node also reports local_gb_used, which is the sum of the allocated
nova instances' flavor disk sizes. (local_gb > local_gb_used).
Try to spawn an instance with a flavor's disk higher than 1.or disk
size of 2 GB on the host.
Expected result
===============
Instance should be in ERROR state, it shouldn't be able to schedule to
the compute node.
Actual result
=============
The instance is active.
Environment
===========
OpenStack Pike.
Hyper-V 2012 R2 compute node.
Logs & Configs
==============
[1] compute node's resource view VS. actual reported resource view:
http://paste.openstack.org/show/621318/
[2] compute node's resources (nova hypervisor-show), spawning an instance:
http://paste.openstack.org/show/621319/
To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1717892/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
