← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2069543] [NEW] instance tap port has dead vlan when parent port for trunk

 

Public bug reported:

zed release, version 21.2.1

i have not tried to reproduce on a newer version


when creating a trunk the tap interface for the instance is still in dead vlan

    Bridge tbr-d0aed4fd-1
        datapath_type: system
        Port tbr-d0aed4fd-1
            Interface tbr-d0aed4fd-1
                type: internal
        Port tap2f072c63-b6
            tag: 4095
            Interface tap2f072c63-b6
        Port tpt-2f072c63-b6
            tag: 0
            Interface tpt-2f072c63-b6
                type: patch
                options: {peer=tpi-2f072c63-b6}

if I issue set tag=[] to force the tap port into being a trunk with:
ovs-vsctl set port tap2f072c63-b6 tag=[]

traffic starts to flow which makes me think the port binding for the tap
is not done correctly

logs: https://paste.opendev.org/show/bstDgfi43ManfW1RijJo/

trunk ID: d0aed4fd-193d-4164-ba48-7d1d137787e1
parent port ID: 2f072c63-b6ce-45d3-96b6-27b4f46d397b

** 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/2069543

Title:
  instance tap port has dead vlan when parent port for trunk

Status in neutron:
  New

Bug description:
  zed release, version 21.2.1

  i have not tried to reproduce on a newer version

  
  when creating a trunk the tap interface for the instance is still in dead vlan

      Bridge tbr-d0aed4fd-1
          datapath_type: system
          Port tbr-d0aed4fd-1
              Interface tbr-d0aed4fd-1
                  type: internal
          Port tap2f072c63-b6
              tag: 4095
              Interface tap2f072c63-b6
          Port tpt-2f072c63-b6
              tag: 0
              Interface tpt-2f072c63-b6
                  type: patch
                  options: {peer=tpi-2f072c63-b6}

  if I issue set tag=[] to force the tap port into being a trunk with:
  ovs-vsctl set port tap2f072c63-b6 tag=[]

  traffic starts to flow which makes me think the port binding for the
  tap is not done correctly

  logs: https://paste.opendev.org/show/bstDgfi43ManfW1RijJo/

  trunk ID: d0aed4fd-193d-4164-ba48-7d1d137787e1
  parent port ID: 2f072c63-b6ce-45d3-96b6-27b4f46d397b

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



Follow ups