yahoo-eng-team team mailing list archive

[Jesse Pretorius <jesse.pretorius@xxxxxxxxx>]

Public bug reported:

Environment:
 - Ubuntu 12.04.3 LTS
 - Grizzly 2013.1.3-0ubuntu1~cloud0
 - Quantum with GRE Tunneling
 - OpenVSwitch 1.4.0-1ubuntu1.5

I'm getting inconsistent implementations of port tags for the Router
internal interfaces and the DHCP's interface when they're created in
OVS.

For example, what I should be seeing is something like this:

        Port "tap7ef1ee95-52"
            tag: 30
            Interface "tap7ef1ee95-52"
                type: internal
        Port "qr-8bfc6675-3a"
            tag: 13
            Interface "qr-8bfc6675-3a"
                type: internal

However, I end up seeing something like this:

        Port "tap2b520e87-5e"
            Interface "tap2b520e87-5e"
                type: internal
        Port "qr-ba0036f3-7e"
            Interface "qr-ba0036f3-7e"
                type: internal

It's not consistently happening - sometimes it actually is done
correctly.

The workaround to repair this is either to manually tag the interfaces,
which can be done if at least one of them was tagged, or to restart
'quantum-plugin-openvswitch-agent', which unfortunately causes a drop in
connectivity for those which were correctly tagged.

Does anyone know under which conditions this issue may occur and whether
there are better workarounds?

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

Title:
  Port tags not reliably implementing

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Environment:
   - Ubuntu 12.04.3 LTS
   - Grizzly 2013.1.3-0ubuntu1~cloud0
   - Quantum with GRE Tunneling
   - OpenVSwitch 1.4.0-1ubuntu1.5

  I'm getting inconsistent implementations of port tags for the Router
  internal interfaces and the DHCP's interface when they're created in
  OVS.

  For example, what I should be seeing is something like this:

          Port "tap7ef1ee95-52"
              tag: 30
              Interface "tap7ef1ee95-52"
                  type: internal
          Port "qr-8bfc6675-3a"
              tag: 13
              Interface "qr-8bfc6675-3a"
                  type: internal

  However, I end up seeing something like this:

          Port "tap2b520e87-5e"
              Interface "tap2b520e87-5e"
                  type: internal
          Port "qr-ba0036f3-7e"
              Interface "qr-ba0036f3-7e"
                  type: internal

  It's not consistently happening - sometimes it actually is done
  correctly.

  The workaround to repair this is either to manually tag the
  interfaces, which can be done if at least one of them was tagged, or
  to restart 'quantum-plugin-openvswitch-agent', which unfortunately
  causes a drop in connectivity for those which were correctly tagged.

  Does anyone know under which conditions this issue may occur and
  whether there are better workarounds?

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