yahoo-eng-team team mailing list archive

[Armando Migliaccio <1756064@xxxxxxxxxxxxxxxxxx>]

Ok, then that makes even less sense. I am not sure I understand why a
nova-compute restart blow up the metadata on the port. I would argue
that this is not a neutron bug but a nova/os-vif bug where not all
metadata are restored upon interface recreation, assumed one is
necessary.

As for your last question: yes, storing trunk details in the interface
external_ids is done for performance lookup reasons. That avoids many
OVSDB queries or even going back to the server. It's build on the
fundamental premise that OVSDB is reliable.

** Changed in: neutron
       Status: Incomplete => Invalid

** Also affects: os-vif
   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/1756064

Title:
  neutron agent doesn't remove trunk bridge after nova-compute restart

Status in neutron:
  Invalid
Status in os-vif:
  New

Bug description:
  env:
  backend is openvswitch with DPDK
  Version is Ocata

  Steps:
  Create two networks.
  Create two ports for each network
  Create trunk port
  boot virtual machine with trunk port
  Restart nova-compute on compute node: #  openstack-service restart openstack-nova-compute
  Remove the virtual machine
  Check ovs configuration on compute node: ovs-vsctl show

  Expected result: there is no trunk bridge e.g. tbr-c4ce71ea-7
  Actual result: trunk bridge and services ports are still in ovs configuration. e.g.

      Bridge "tbr-c4ce71ea-7"
          Port "spt-63eb23e7-af"
              tag: 102
              Interface "spt-63eb23e7-af"
                  type: patch
                  options: {peer="spi-63eb23e7-af"}
          Port "tbr-c4ce71ea-7"
              Interface "tbr-c4ce71ea-7"
                  type: internal
          Port "tpt-d6c0e47e-ed"
              Interface "tpt-d6c0e47e-ed"
                  type: patch
                  options: {peer="tpi-d6c0e47e-ed"}

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