← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1837756] Re: ImagePropertiesFilter: hypervisor_type matchmaking not compliant with documentation

 

** Changed in: nova
   Importance: Undecided => High

** Also affects: nova/rocky
   Importance: Undecided
       Status: New

** Also affects: nova/stein
   Importance: Undecided
       Status: New

** Tags added: libvirt scheduler upgrade

** Changed in: nova/rocky
       Status: New => Triaged

** Changed in: nova/stein
       Status: New => Triaged

** Changed in: nova/stein
   Importance: Undecided => High

** Changed in: nova/rocky
   Importance: Undecided => High

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

Title:
  ImagePropertiesFilter:  hypervisor_type matchmaking not compliant with
  documentation

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) rocky series:
  Triaged
Status in OpenStack Compute (nova) stein series:
  Triaged

Bug description:
  All compute nodes of my Cloud are configured using
  libvirt]/virt_type=kvm

  Please note that this is not exposed in the 'openstack hypervisor list
  --long' output which reports QEMU as  'Hypervisor Type'.

  
  I have some images with the following property:

  hypervisor_type='qemu'

  
  No problems scheduling instances using these images in Ocata.
  After having updated to Rocky, the ImagePropertiesFilter filters out all the compute nodes, because they offer 'kvm' while 'qemu' is requested.

  This is not compliant with documentation.
  Both Nova (https://docs.openstack.org/nova/rocky/admin/configuration/schedulers.html) and Glance (https://docs.openstack.org/glance/latest/admin/useful-image-properties.html) documentation say that  qemu is supposed to be used for both QEMU and KVM hypervisor types.

  
  The issue is discussed in:

  
  http://lists.openstack.org/pipermail/openstack-discuss/2019-July/thread.html#7842

  where it is reported that the new behavior is likely because this
  change:

  https://review.opendev.org/531347

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


References