yahoo-eng-team team mailing list archive

[Edward Hope-Morley <1931244@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have an Openstack Ussuri 16.3.2 deployment using OVN. When I create a
vm with one or more sriov ports it fails with:

2021-06-08 11:38:31.939 526862 WARNING nova.virt.libvirt.driver [req-
c4be797e-7d7e-4e73-8406-f74ae51db192 696c98b722a44d229e16b6d6474a27d4
0b9102977dcc4d4ab662b48494bb3110 - 2e0bf6ec95c047d986a61f7570222149
2e0bf6ec95c047d986a61f7570222149] [instance: 7ab9b374-51eb-
4e94-8055-c69e8a7d76b3] Timeout waiting for [('network-vif-plugged',
'c2b7c68d-c465-4ca2-869a-59bc73b2b595'), ('network-vif-plugged',
'a50de16a-29ac-4dca-9cb6-0247a932fbf3')] for instance with vm_state
building and task_state spawning.: eventlet.timeout.Timeout: 300 seconds

A bit of analysis shows that nova-compute did its thing and sits there
waiting on network-vif-plugged. The sriov-agent then notices new VFs
configured and sends a get_devices_details_list() rpc call to neutron
and neutron never responds. Reverting to 16.3.1 fixes the issue. Taking
a closer look at 16.3.2 by reverting patches lead to [1] as the culprit.

[1]
https://github.com/openstack/neutron/commit/7cf9597570f288d27768dc5ff7be04824d09f8bc

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  ovn sriov broken from ussuri onwards

Status in neutron:
  New

Bug description:
  I have an Openstack Ussuri 16.3.2 deployment using OVN. When I create
  a vm with one or more sriov ports it fails with:

  2021-06-08 11:38:31.939 526862 WARNING nova.virt.libvirt.driver [req-
  c4be797e-7d7e-4e73-8406-f74ae51db192 696c98b722a44d229e16b6d6474a27d4
  0b9102977dcc4d4ab662b48494bb3110 - 2e0bf6ec95c047d986a61f7570222149
  2e0bf6ec95c047d986a61f7570222149] [instance: 7ab9b374-51eb-
  4e94-8055-c69e8a7d76b3] Timeout waiting for [('network-vif-plugged',
  'c2b7c68d-c465-4ca2-869a-59bc73b2b595'), ('network-vif-plugged',
  'a50de16a-29ac-4dca-9cb6-0247a932fbf3')] for instance with vm_state
  building and task_state spawning.: eventlet.timeout.Timeout: 300
  seconds

  A bit of analysis shows that nova-compute did its thing and sits there
  waiting on network-vif-plugged. The sriov-agent then notices new VFs
  configured and sends a get_devices_details_list() rpc call to neutron
  and neutron never responds. Reverting to 16.3.1 fixes the issue.
  Taking a closer look at 16.3.2 by reverting patches lead to [1] as the
  culprit.

  [1]
  https://github.com/openstack/neutron/commit/7cf9597570f288d27768dc5ff7be04824d09f8bc

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