yahoo-eng-team team mailing list archive

[OpenStack Infra <1831622@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/663031
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c148c6df468b3ee1a274f191fb4317aef2e4b225
Submitter: Zuul
Branch:    master

commit c148c6df468b3ee1a274f191fb4317aef2e4b225
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date:   Tue Jun 4 12:57:48 2019 +0400

    SRIOV agent: wait VFs initialization on embedded switch create
    
    Check for configured and actual number of VFs to prevent
    device registaration with 0 VFs.
    
    Closes-Bug: #1831622
    Change-Id: Ie699d245f8ae2fc1d16b96432d2962788d9dba57


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1831622

Title:
  SRIOV: agent may not register VFs

Status in neutron:
  Fix Released

Bug description:
  When a VM instantiated with a PF-PT (direct-physical) port, the
  Neutron SR-IOV agent removes the respective embedded switch device
  instance from the switch manager. After the VM releases the PF, the
  associated device (sys/class/net/<device>) appears immediately, but
  the initialization of its VFs and the creation of the appropriate
  sysfs entries (/sys/class/net/<device>/device/virtfn<#vf>) may even
  take more than a second, depending on the platform and the NIC's
  kernel driver capabilities. The Neutron SR-IOV agent eagerly tries to
  discover and register NIC devices, that are not blacklisted and not
  yet known, by creating the respective embedded switch instances and
  enumerating the avalable VFs underneat them. However, when it is done
  in an early phase, where the sysfs entries for the VFs are not yet
  present, because the PF has just been released, then a port-less
  embedded switch will be created to represent that device. As a
  consequence, port updates that target VFs which are supposed to belong
  to a incorrectly registered embedded device, won't be treated properly
  by the agent, causing a VM instantiation timeout.

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