[Bug 1931244] Please test proposed package

[Corey Bryant]

Hello Edward, or anyone else affected,

Accepted neutron into wallaby-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:wallaby-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-wallaby-needed to verification-wallaby-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-wallaby-failed. In either case, details
of your testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/ussuri
       Status: Triaged => Fix Committed

** Tags added: verification-ussuri-needed

** Changed in: cloud-archive/wallaby
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1931244

Title:
  ovn sriov broken from ussuri onwards

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  Invalid
Status in Ubuntu Cloud Archive wallaby series:
  Fix Committed
Status in Ubuntu Cloud Archive xena series:
  Fix Committed
Status in neutron:
  In Progress
Status in neutron package in Ubuntu:
  Triaged
Status in neutron source package in Focal:
  Fix Committed
Status in neutron source package in Hirsute:
  Fix Committed
Status in neutron source package in Impish:
  Triaged

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

  === Ubuntu SRU details ===
  [Impact]
  [Test Case]
  See above.
  I think for testing we can run standard regression testing with OVN/neutron deployments plus tempest testing.

  For now we are planning to revert the commit as a stop-gap to prevent
  further upgrades from being regressed.

  [Regression Potential]
  There is regression potential in that the patch being reverted contributes partial fixes to the following related bugs. Considering most openstack users are on ussuri at this point and 16.3.2 has not been available for very long the revert that we are proposing would seem to have the least amount of regression potential.
  https://bugs.launchpad.net/neutron/+bug/1894117
  https://bugs.launchpad.net/neutron/+bug/1903008

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