SNAT port not found for the given internal port error message seen when gateway is removed for DVR routers.

[Swaminathan Vasudevan]

Recently the logstash logs showed traces about "SNAT port not found for the given internal port".

http://logs.openstack.org/22/219422/13/check/gate-tempest-dsvm-neutron-dvr/e5243b2/logs/screen-q-l3.txt.gz?level=TRACE#_2015-09-15_12_28_08_880

By analyzing the failure it seems when a gateway is removed, the "get_snat_port_for_internal_port" is called without the cache value.

This bug was introduced by the patch shown below.

Icc099c1a97e3e68eeaf4690bc83167ba30d8099a

[Swaminathan Vasudevan (swaminathan-vasudevan)]

This will affect Liberty.

[Kyle Mestery (mestery)]

Is there a patch for this? Given we're near the end of Liberty, is this a bug we'd hold the RC1 for? I don't think so, so if it doesn't merge by Friday we'll keep it out of the release.

[Kyle Mestery (mestery)]

Also, I don't see the patch linked here in the bug, can someone do that please?

[Swaminathan Vasudevan (swaminathan-vasudevan)]

Yes we do have a patch for this right now.

https://review.openstack.org/#/c/224250/

[OpenStack Infra (hudson-openstack)]

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

commit e0664a4c2cd8ec5e24f67eac2b2c4e04464888d3
Author: Swaminathan Vasudevan <email address hidden>
Date: Wed Sep 16 11:13:46 2015 -0700

    Fixes SNAT port not found for internal port

    For every router interface added to a router
    with a default gateway there will be an internal
    SNAT port generated and will be required by the
    L3 Agent to process the SNAT rules.

    This bug was introduced by the change ID below
    Icc099c1a97e3e68eeaf4690bc83167ba30d8099a.

    When the gateway is removed these ports have to
    be removed from the namespace. These ports are
    cached in the router_info and should be provided
    to the get_snat_port_for_internal_port function
    when called from external_gateway_removed or when
    called from _dvr_internal_network_removed.

    This patch fixes this problem.

    Closes-Bug: #1496578

    Change-Id: Id5af4774ba246e24f343f5623af5ea9143bd5f6b