yahoo-eng-team team mailing list archive

[OpenStack Infra <1795127@xxxxxxxxxxxxxxxxxx>]

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 <liuyul@xxxxxxxxxxxxxxx>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1795127

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

Status in neutron:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1795127/+subscriptions