OVS Agent: With l2-pop ON, cleaned up tunnel ports appear in rules for table 0 in br-tun

[Vivekanandan Narasimhan]

When neutron Openswitch agent runs with l2pop ON, it is not removing flows from table 0 of br-tun, those flow sthat carry cleaned up tunnel ports by l2-pop.

Impact of this bug: Explosion of flow rules in br-tun table 0 as tunnel ports come-in and go-away in a scaled environment

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/93624

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/93624
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3f9658dcd9b2cccdc0f03088723305c980130cd3
Submitter: Jenkins
Branch: master

commit 3f9658dcd9b2cccdc0f03088723305c980130cd3
Author: Vivekanandan Narasimhan <email address hidden>
Date: Wed May 14 12:06:45 2014 -0700

    When l2-pop ON, clean stale ports in table0 br-tun

    When l2-pop is turned ON, the tunnels towards a
    specific node are created and torn down by other nodes,
    based on availability of ports on that specific node in
    specific networks. This generally reclaims the resources
    used for such tunnels in all the nodes.

    Under such conditions, in the current code (without this
    fix), the cleaned up ports continue to be present in
    rules of table0 of br-tun, resulting in flow explosion.

    This fix adds cleanup-logic to remove such rules that
    continue to use l2-pop cleaned up ports, from table0 of
    br-tun.

    Change-Id: I2639ff6432a13320adcadbcc0841319a99ce8c24
    Closes-Bug: #1318261