yahoo-eng-team team mailing list archive

[OpenStack Infra <1794305@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/605358
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=656a8f872970013ff4c0bc577266cbe7f0343037
Submitter: Zuul
Branch:    master

commit 656a8f872970013ff4c0bc577266cbe7f0343037
Author: LIU Yulong <liuyul@xxxxxxxxxxxxxxx>
Date:   Wed Sep 26 15:58:11 2018 +0800

    Do not install centralized FIP if HA port is down
    
    The issue scenario happens when we disassociate a floating IP
    while the 'master' router host is restarted or powered-off.
    
    When the L3 agent is powered-on again, the HA router state config
    still remains 'master', but the ha port is down. And the message
    queue still has one 'router_update' message (floating IP
    disassociate message), so the L3 agent will sync this router info
    at least twice during the restart, one is the router_update, the
    other is the L3 agent full-sync.
    
    The first one will add the centralized FIP to the qg-device, because
    the router state is 'master'. So for DVR HA routers, only add the
    centralized floating IP to the qg-device in the snat-namespace when
    the HA port is up. For the restart procedure, if the HA port is up,
    but the router is set to 'backup', do not add the floating IP.
    
    Closes-Bug: #1794305
    Change-Id: Ib39fe7dcd437a867c69852885c461a594167f6a1


** 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/1794305

Title:
  [dvr_no_external][ha] centralized fip show up in the backup snat-
  namespace on the restore host (restaring or down/up)

Status in neutron:
  Fix Released

Bug description:
  ENV:
  platform: centos7.5
  kernel: 3.10.0-862.11.6.el7.x86_64
  neutron: master
  openstack: devstack multi-node master

  Problem:
  The centralized fip will show up in the snat namespace if the host backing online.

  Reproduce:
  (1) create dvr + ha router, and connected to the private subnet and public network.
  (2) associate 2 floating IPs (fip-1, fip-2) to two VMs hosting on the dvr_no_external host
  (3) shutdown the `master` router hosting on physic host-2
  (4) dis-associate one floating IP (fip-2) from the VM
  (5) start the physic host
  (6) let l3 agent processing and sync the routers

  Then you can see the floating IP (fip-1) is show up in the started
  host-2 snat-namespace.

  Some outputs:
  http://paste.openstack.org/show/730727/

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