DVR: csnat portion is not rescheduled after snat host goes down

Bug #1472205 reported by Oleg Bondarev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Oleg Bondarev

Bug Description

Currently l3 auto rescheduling mechanism does not take into account DVR router csnat portion.
So if l3 agent (node) hosting csnat portion of a dvr router goes down, external connectivity is lost for all VMs without floating IPs.

Changed in neutron:
status: New → In Progress
Changed in neutron:
assignee: Oleg Bondarev (obondarev) → Ryan Moats (rmoats)
Changed in neutron:
assignee: Ryan Moats (rmoats) → Oleg Bondarev (obondarev)
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/211939

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

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

commit 4418bf426ac48935b27d235139912c2e3ec1d1b5
Author: Oleg Bondarev <email address hidden>
Date: Wed Aug 12 12:29:25 2015 +0300

    DVR: fix router rescheduling on server side

    This fixes router rescheduling for dvr routers to
    correctly handle CSNAT portion rescheduling on server side.

    Next patch will make L3 agent aware of possible SNAT role
    rescheduling to/from it.

    Partial-Bug: #1472205
    Change-Id: I069500a2f1de9a734124544a3f2d793e9fa2d27c

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

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

commit a264b329df82f3c391f75bd9ad73a1327616a43d
Author: Oleg Bondarev <email address hidden>
Date: Tue Jul 7 13:36:00 2015 +0300

    DVR: fix router rescheduling on agent side

    The patch makes L3 agent aware of possible SNAT role
    rescheduling to/from it.
    The gist is to compare gw_port host change.
    If it was changed and agent is not on target host then
    it needs to clear snat namespace if one exists. If agent
    is on target host it needs to create snat namespace from
    scratch if it doesn't exist.

    Host field was excluded from gw_port comparison on
    agent side as part of HA Router feature implementation.
    This code was moved to corresponding module.

    Closes-Bug: #1472205
    Change-Id: I840bded9eb547df014c6fb2b4cbfe4a876b9b878

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (feature/pecan)

Fix proposed to branch: feature/pecan
Review: https://review.openstack.org/218710

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (feature/pecan)
Download full text (155.6 KiB)

Reviewed: https://review.openstack.org/218710
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c5f44e1b3bd4ed8a0b7232fd293b576cc8c1c87
Submitter: Jenkins
Branch: feature/pecan

commit f35d1c5c50dccbef1a2e079f967b82f0df0e22e9
Author: Adelina Tuvenie <email address hidden>
Date: Thu Aug 27 02:27:28 2015 -0700

    Fixes wrong neutron Hyper-V Agent name in constants

    Change Id03fb147e11541be309c1cd22ce27e70fadc28b5 moved the
    AGENT_TYPE_HYPERV constant from common.constants to
    plugins.ml2.drivers.hyperv.constants but change the value of the
    constant from 'HyperV agent' to 'hyperv'. This patch changes
    the name back to 'HyperV agent'

    Change-Id: If74b4b2a84811e266c8b12e70bf6bfe74ed4ea21
    Partial-Bug: #1487598

commit de604de334854e2eb6b4312ff57920564cbd4459
Author: OpenStack Proposal Bot <email address hidden>
Date: Sun Aug 30 01:39:06 2015 +0000

    Updated from global requirements

    Change-Id: Ie52aa3b59784722806726e4046bd07f4a4d97328

commit f0415ac20eaf5ab4abb9bd4839bf6d04ceee85d0
Author: armando-migliaccio <email address hidden>
Date: Fri Aug 28 13:53:04 2015 -0700

    Revert "Add support for unaddressed port"

    This implementation may expose a vulnerability where a malicious
    user can sieze the opportunity of a time window where a port
    may land unaddressed on a shared network, thus allowing him/her
    to suck up all the tenant traffic he/she wants....oh the shivers.

    This reverts commit d4c52b7f5a36a103a92bf9dcda7f371959112292.

    Change-Id: I7ebdaa8d3defa80eab90e460fde541a5bdd8864c

commit 013fdcd2a6d45dbe4de5d6e7077e5e9b60985ef9
Author: Assaf Muller <email address hidden>
Date: Fri Aug 28 16:41:07 2015 -0400

    Improve logging upon failure in iptables functional tests

    This will help us nail down a more accurate and efficient logstash
    query.

    Change-Id: Iee4238e358f7b056e373c7be8d6aa3202117a680
    Related-Bug: #1478847

commit 622dea818d851224a43d5276a81d5ce8a6eebb76
Author: Ivar Lazzaro <email address hidden>
Date: Mon Aug 17 17:17:42 2015 -0700

    handle gw_info outside of the db transaction on router creation

    Move the gateway interface creation outside the DB transaction
    to avoid lock timeout.

    Change-Id: I5a78d7f32e8ca912016978105221d5f34618af19
    Closes-bug: 1485809

commit 5b27d290a0a95f6247fc5a0fe6da1e7d905e6b2d
Author: Assaf Muller <email address hidden>
Date: Wed Aug 26 10:07:03 2015 -0400

    Remove ml2 resource extension success logging

    This is the cause of a tremendous amount of logs, for no
    perceivable gain. A normal dvr run in the gate shows this debug
    message around 120K times, which is way too much.

    Closes-Bug: #1489952

    Change-Id: I26fca8515d866a7cc1638d07fa33bc04479ae221

commit 8d3faf549cba2f58c872ef4121b2481e73464010
Author: huangpengtao <email address hidden>
Date: Fri Aug 28 23:20:46 2015 +0800

    Replace "prt" variable by "port"

    the local variable prt is meaningless,
    and port is used popular.

    Change-Id: I20849102cf5b4d84433c46791b4b1e2a22dc4739

commit ee374e7a5f4dea538fcd942f5...

tags: added: in-feature-pecan
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → liberty-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: liberty-3 → 7.0.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/242647

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

Reviewed: https://review.openstack.org/242647
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b0d40f440175a417ba3b08cdeba25b54afc565fb
Submitter: Jenkins
Branch: stable/kilo

commit b0d40f440175a417ba3b08cdeba25b54afc565fb
Author: Oleg Bondarev <email address hidden>
Date: Wed Aug 12 12:29:25 2015 +0300

    DVR: fix router rescheduling on server side

    This fixes router rescheduling for dvr routers to
    correctly handle CSNAT portion rescheduling on server side.

    Next patch will make L3 agent aware of possible SNAT role
    rescheduling to/from it.

    Partial-Bug: #1472205
    Change-Id: I069500a2f1de9a734124544a3f2d793e9fa2d27c
    (cherry picked from commit 4418bf426ac48935b27d235139912c2e3ec1d1b5)

tags: added: in-stable-kilo
Revision history for this message
Carl Baldwin (carl-baldwin) wrote :

Seems like another bug that wouldn't have happened if the router binding were done correctly in the first place.

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.