Midonet plugin: Source NAT not applied

Bug #1261665 reported by Dave Cahill
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Dave Cahill

Bug Description

Steps:
Using the MidoNet plugin:
* Create a private network
* Create a VM on the private network
* Create a router
* Create an interface for the router on the private network
* Create an external network
* Set a router's gateway to the external network
* Ping a publicly routable address from a VM on a network attached the router

Observed:
Source NAT is not applied to the outbound traffic

Expected:
Outbound traffic should be source NATted at the router

Dave Cahill (dcahill-f)
Changed in neutron:
assignee: nobody → Dave Cahill (dcahill-f)
Dave Cahill (dcahill-f)
tags: added: havana-backport-potential
Akihiro Motoki (amotoki)
tags: added: midonet
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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

commit 7dc3c671656974596b9a373c911e5b786d57be35
Author: Dave Cahill <email address hidden>
Date: Tue Dec 17 05:52:48 2013 +0000

    Midonet plugin: Fix source NAT

    Source NAT rule was being applied on the incorrect port.
    It was being applied to the Neutron gateway port, not to
    the MidoNet tenant / provider router link port.

    Change-Id: Ib818c09adfb6957b7cad4523e5ce1fdffde9590b
    Closes-Bug: #1261665

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → icehouse-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-2 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.