← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1895671] [NEW] [OVN] test_add_interface_in_use fail with OVN

 

Public bug reported:

The test neutron-tempest-plugin test_add_interface_in_use fails when
ml2/ovn is used.

Apparently this behavior is a consequence of this fix:
https://review.opendev.org/#/c/724930, reverting the patch makes it work
again BUT, reverting it will re-introduce the original bug that the
patch fixed.

Basically what happens is that now the add_router_interface() method
from ml2/ovn will never raise the PortInUse exception if you try to add
the same interface twice. The test_add_interface_in_use is a negative
test that validates this behavior.

This idempotent behavior was introduced because of the maintenance
thread but I believe that we can make the API behave as expected
(raising the PortInUse) and the maintenance code can handle this
exception and ignore it.

** Affects: neutron
     Importance: High
         Status: Confirmed

** Changed in: neutron
       Status: New => Confirmed

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

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

Title:
  [OVN] test_add_interface_in_use fail with OVN

Status in neutron:
  Confirmed

Bug description:
  The test neutron-tempest-plugin test_add_interface_in_use fails when
  ml2/ovn is used.

  Apparently this behavior is a consequence of this fix:
  https://review.opendev.org/#/c/724930, reverting the patch makes it
  work again BUT, reverting it will re-introduce the original bug that
  the patch fixed.

  Basically what happens is that now the add_router_interface() method
  from ml2/ovn will never raise the PortInUse exception if you try to
  add the same interface twice. The test_add_interface_in_use is a
  negative test that validates this behavior.

  This idempotent behavior was introduced because of the maintenance
  thread but I believe that we can make the API behave as expected
  (raising the PortInUse) and the maintenance code can handle this
  exception and ignore it.

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


Follow ups