← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1841514] [NEW] disk_io_limits settings are not reflected when resize using vmware driver

 

Public bug reported:

Description
===========
We found that disk_io_limits settings are not reflected when resize using vmware driver.

Steps to reproduce
==================
* I did command resize using CLI or horizon
* then VM status VERIFY_RESIZE with no problem
* then I did command resize-confirm
* It looks like it worked

* But when I check vCenter, IOPS has not changed

Expected result
===============
* IOPS settings are configured for the resized VM

Actual result
=============
* IOPS settings are not configured for the resized VM

Environment
===========
1. Exact version of OpenStack you are running.
* Community OpenStack Mitaka

2. Which hypervisor did you use?
* VMware

3. Which networking type did you use?
* Neutron ML2 Driver For VMWare vCenter DVS

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1841514

Title:
  disk_io_limits settings are not reflected when resize using vmware
  driver

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  We found that disk_io_limits settings are not reflected when resize using vmware driver.

  Steps to reproduce
  ==================
  * I did command resize using CLI or horizon
  * then VM status VERIFY_RESIZE with no problem
  * then I did command resize-confirm
  * It looks like it worked

  * But when I check vCenter, IOPS has not changed

  Expected result
  ===============
  * IOPS settings are configured for the resized VM

  Actual result
  =============
  * IOPS settings are not configured for the resized VM

  Environment
  ===========
  1. Exact version of OpenStack you are running.
  * Community OpenStack Mitaka

  2. Which hypervisor did you use?
  * VMware

  3. Which networking type did you use?
  * Neutron ML2 Driver For VMWare vCenter DVS

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1841514/+subscriptions


Follow ups