yahoo-eng-team team mailing list archive

[sean mooney <1883671@xxxxxxxxxxxxxxxxxx>]

reading the nic feature flags was intoduced in pike 
https://github.com/openstack/nova/commit/e6829f872aca03af6181557260637c8b601e476a

but this only seams to happen on mondern version of libvirt so setting
as wont fix. it can be backported if someone hits the issue and care to
do so

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

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

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

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

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

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

** Changed in: nova/pike
       Status: New => Won't Fix

** Changed in: nova/queens
       Status: New => Won't Fix

** Changed in: nova/rocky
       Status: New => Won't Fix

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

** Changed in: nova/stein
       Status: Triaged => Won't Fix

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

Title:
  [SRIOV] When a VF is bound to a VM, Nova can't retrieve the PCI info

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  Won't Fix
Status in OpenStack Compute (nova) queens series:
  Won't Fix
Status in OpenStack Compute (nova) rocky series:
  Won't Fix
Status in OpenStack Compute (nova) stein series:
  Won't Fix
Status in OpenStack Compute (nova) train series:
  Triaged
Status in OpenStack Compute (nova) ussuri series:
  Triaged

Bug description:
  Nova periodically updates the available resources per hypervisor [1].
  That implies the reporting of the PCI devices [2]->[3].

  In [4], a new feature was introduced to read from libvirt the NIC
  capabilities (gso, tso, tx, etc.). But when the NIC interface is bound
  to the VM and the MAC address is not the one assigned by the driver
  (Nova changes the MAC address according to the info provided by
  Neutron), libvirt fails reading the non-existing device:
  http://paste.openstack.org/show/794799/.

  This command should be avoided or at least, if the executing fails,
  the exception could be hidden.

  
  [1]https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L9642
  [2]https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6980
  [3]https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6898
  [4]Ia5b6abbbf4e5f762e0df04167c32c6135781d305

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