unable to ping floating ip from fixed_ip association

Bug #1221419 reported by Aaron Rosen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Salvatore Orlando
Havana
Fix Released
High
Aaron Rosen

Bug Description

Currently if one checks out a floating ip the instance that is associated with that floating ip is unable to ping it.

Tags: nicira
Aaron Rosen (arosen)
Changed in neutron:
importance: Undecided → Critical
importance: Critical → High
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/45321

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

Reviewed: https://review.openstack.org/45321
Committed: http://github.com/openstack/neutron/commit/37388cc074b21a808ac7513d1f60ec681872b47c
Submitter: Jenkins
Branch: master

commit 37388cc074b21a808ac7513d1f60ec681872b47c
Author: Aaron Rosen <email address hidden>
Date: Thu Sep 5 13:22:46 2013 -0700

    Fix unable to ping floating ip from internal_ip

    The following patch adds a no-dnat rule so that an internal_ip
    can communicate with it's floatingip.

    Fixes bug: 1221419

    Change-Id: I3899b01f316902d1139e47b153aadb7ecb1ff983

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: havana-rc1 → 2013.2
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

Reopening as the previous fix did not prove effective.

Changed in neutron:
milestone: 2013.2 → icehouse-1
status: Fix Released → Confirmed
assignee: Aaron Rosen (arosen) → Salvatore Orlando (salvatore-orlando)
tags: added: grizzly-backport-potential havana-backport-potential
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/56847

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

Reviewed: https://review.openstack.org/56847
Committed: http://github.com/openstack/neutron/commit/ed2e32b03123ae8e7555b997152c1d8d941494f2
Submitter: Jenkins
Branch: master

commit ed2e32b03123ae8e7555b997152c1d8d941494f2
Author: Salvatore Orlando <email address hidden>
Date: Sun Nov 17 16:59:06 2013 -0800

    NVP plugin:fix connectivity to fip from internal nw

    The current set of NAT rules configured in the NVP logical router
    prevents instances on an internal network from establishing TCP
    connections with a floating IP associate with an internal port
    on the same Neutron network.

    This patch add a SNAT rule to ensure connections coming from the
    internal network always appear to the port associate with the
    floating IP as coming from the external network.

    Change-Id: I12da12ee136c61fddb04f2b216382b51d751a02c
    Closes-Bug: 1221419

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/havana)

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/66082

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/havana)

Reviewed: https://review.openstack.org/66082
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b5c4152ac9958e173d785894f96f34704b6641c2
Submitter: Jenkins
Branch: stable/havana

commit b5c4152ac9958e173d785894f96f34704b6641c2
Author: Salvatore Orlando <email address hidden>
Date: Sun Nov 17 16:59:06 2013 -0800

    NVP plugin:fix connectivity to fip from internal nw

    The current set of NAT rules configured in the NVP logical router
    prevents instances on an internal network from establishing TCP
    connections with a floating IP associate with an internal port
    on the same Neutron network.

    This patch add a SNAT rule to ensure connections coming from the
    internal network always appear to the port associate with the
    floating IP as coming from the external network.

    Change-Id: I12da12ee136c61fddb04f2b216382b51d751a02c
    Closes-Bug: 1221419
    (cherry picked from commit ed2e32b03123ae8e7555b997152c1d8d941494f2)

tags: added: in-stable-havana
Alan Pevec (apevec)
tags: removed: grizzly-backport-potential havana-backport-potential in-stable-havana
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-1 → 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.