yahoo-eng-team team mailing list archive

[Jakub Libosvar <libosvar@xxxxxxxxxx>]

Public bug reported:

Description of problem:
See 'Steps to Reproduce' below.

The external port is deleted from the port_binding table instead of
chassis removed and then deleted so the PortBindingUpdate event is never
generated.

The metadata agent reacts on Port Binding Update event only. That means when there is a VM and we delete it, it first calls port update to remove the chassis from the port binding, so the port binding is chassis=[] before the PB gets deleted.
In SRIOV scenario we don't do that and we delete a port that is bound.

We need a special event for the sriov deletion case.


Steps to Reproduce:
1. create an SRIOV port on either a tenant or a prov network + create a VM attached to that port - check ovn metadata namespace has been created on a GW node
2. remove that VM - the ovn metadata namespace is not removed from that GW node
3. even after removing the port, the namespace is not removed

Actual results:
OVN metadata namespaces clean up mechanism not working with SRIOV ports

Expected results:
Namespaces should be removed after port is removed

** Affects: neutron
     Importance: Undecided
     Assignee: Jakub Libosvar (libosvar)
         Status: New


** Tags: ovn

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

Title:
  SRIOV OVN metadata namespaces not cleaned up after ports are unbounded

Status in neutron:
  New

Bug description:
  Description of problem:
  See 'Steps to Reproduce' below.

  The external port is deleted from the port_binding table instead of
  chassis removed and then deleted so the PortBindingUpdate event is
  never generated.

  The metadata agent reacts on Port Binding Update event only. That means when there is a VM and we delete it, it first calls port update to remove the chassis from the port binding, so the port binding is chassis=[] before the PB gets deleted.
  In SRIOV scenario we don't do that and we delete a port that is bound.

  We need a special event for the sriov deletion case.

  
  Steps to Reproduce:
  1. create an SRIOV port on either a tenant or a prov network + create a VM attached to that port - check ovn metadata namespace has been created on a GW node
  2. remove that VM - the ovn metadata namespace is not removed from that GW node
  3. even after removing the port, the namespace is not removed

  Actual results:
  OVN metadata namespaces clean up mechanism not working with SRIOV ports

  Expected results:
  Namespaces should be removed after port is removed

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