yahoo-eng-team team mailing list archive

[Balazs Gibizer <1982945@xxxxxxxxxxxxxxxxxx>]

Nova only acts based on the qos policy from cinder. So I'm moving this
bug to cinder. I suspect that this is either a doc bug on cinder to
state in the doc that these qos configs needs to be set together (e.g.
total_iops_sec_max needs to be set together with total_iops_sec) or
maybe a cinder change that validates on the qos API that valid pairs are
set.

** Project changed: nova => cinder

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

Title:
  cannot start vm from disk with burst qos

Status in Cinder:
  New

Bug description:
  when trying to run a VM from a disk associated with burst qos
  consumer=both total_iops_sec_max=200 , nova/libvirt reports:

  Failed to start libvirt guest: libvirt.libvirtError: internal error:
  unable to execute QEMU command 'block_set_io_throttle':
  bps_max/iops_max require corresponding bps/iops values

  Also when setting up size_iops_sec:
  nova.virt.libvirt.guest libvirt.libvirtError: internal error: unable to execute QEMU command 'block_set_io_throttle': iops size requires an iops value to be set

  OpenStack Yoga, CentOS Stream 8
  libvirt 8.0.0-2
  qemu 6.2.0-5
  cinder backend: lvm (can be any other iscsi storage as well)

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