[dvr][ha] router state change cause unnecessary router_update

Bug #1795127 reported by LIU Yulong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
LIU Yulong

Bug Description

ENV:
devstack multinode master

Problem:
If dvr ha router have a state change event, the l3 agent will get unnecessary router_update message.

Example:
For dvr ha router, assuming it connected to public network and private network.
In dvr_snat namespace, this router will have sg-device and qg-device in the snat namespace.
When a HA state change happened. The sg-device related port and qg-device related port will update port binding host. Each one will send a router_update message to dvr_snat node. This will cause dvr ha router be process multipe times.

Reproduce:
kill the router 'master' keepalived instance in the dvr_snat node, manually produce a HA router state change.

LIU Yulong (dragon889)
Changed in neutron:
assignee: nobody → LIU Yulong (dragon889)
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/606385

Changed in neutron:
status: New → In Progress
LIU Yulong (dragon889)
description: updated
tags: added: l3-dvr-backlog
Changed in neutron:
importance: Undecided → Low
LIU Yulong (dragon889)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/606385
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=452b2824125641128b5297fcf84de090e0763740
Submitter: Zuul
Branch: master

commit 452b2824125641128b5297fcf84de090e0763740
Author: LIU Yulong <email address hidden>
Date: Sat Sep 29 18:04:10 2018 +0800

    Trigger router update only when gateway port IP changed

    During the ha router state change event, the gateway port only
    changed the L2 binding host. So l3 agent has the entire gateway
    port information. It is not necessary to send a router_update
    message to l3 agent again.

    Closes-Bug: #1795127
    Change-Id: Ia332421aff995f42e7a6e6e96b74be1338d54fe1

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 14.0.0.0b1

This issue was fixed in the openstack/neutron 14.0.0.0b1 development milestone.

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

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/705421

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

Reviewed: https://review.opendev.org/705421
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=4f7e1f6b9fa92a99d0a5df7e7440d62df3f51748
Submitter: Zuul
Branch: stable/rocky

commit 4f7e1f6b9fa92a99d0a5df7e7440d62df3f51748
Author: LIU Yulong <email address hidden>
Date: Sat Sep 29 18:04:10 2018 +0800

    Trigger router update only when gateway port IP changed

    During the ha router state change event, the gateway port only
    changed the L2 binding host. So l3 agent has the entire gateway
    port information. It is not necessary to send a router_update
    message to l3 agent again.

    Depends-On: https://review.opendev.org/708825/
    Closes-Bug: #1795127
    Change-Id: Ia332421aff995f42e7a6e6e96b74be1338d54fe1
    (cherry picked from commit 452b2824125641128b5297fcf84de090e0763740)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 13.0.7

This issue was fixed in the openstack/neutron 13.0.7 release.

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.