HyperV Compute driver doesn't return disk stats properly

Bug #1077922 reported by Luis Fernández Álvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Luis Fernández Álvarez

Bug Description

The current version of the HyperV Compute driver returns the disk stats about the C: drive always. The information about the disk stats should point to the disk that is storing the instances.

This problem leads to an inconsistent node status in the controller, not reflecting the current usage.

In order to solve this, it's proposed to extract the disk drive from the config parameter "instance_path".

Changed in nova:
assignee: nobody → Luis Fernandez (luis-fernandez-alvarez)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/15879

Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/15879
Committed: http://github.com/openstack/nova/commit/3d09a28ceca8bf0e594fc103f977e844071e3ea8
Submitter: Jenkins
Branch: master

commit 3d09a28ceca8bf0e594fc103f977e844071e3ea8
Author: Luis Fernandez Alvarez <email address hidden>
Date: Mon Nov 12 14:35:12 2012 +0100

    Fixed HyperV to get disk stats of instances drive

    It fixes bug 1077922

    The current version of the HyperV Compute driver was returning the disk stats about the C: drive always.

    This patch makes HyperV driver extract the current drive from the flag 'instances_path'.

    In order to optimize the procedure, the disk stats extraction is also unified in one method.

    Change-Id: I4920cf2cc07d0f514c0358144b7bceb15d439a63

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-1 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.