yahoo-eng-team team mailing list archive

[OpenStack Infra <1793529@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/606384
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1973a037c29b0fc8bf6347771ed930726d1648f5
Submitter: Zuul
Branch:    master

commit 1973a037c29b0fc8bf6347771ed930726d1648f5
Author: LIU Yulong <liuyul@xxxxxxxxxxxxxxx>
Date:   Fri Sep 28 18:33:28 2018 +0800

    Fix dvr ha router gateway goes wrong host
    
    During L3 agent restart, the dvr ha router gateway port
    binding host may change because the multiple ha router
    scheduled hosts.
    
    After this patch, we return the 'master' ha binding host
    directly during the gateway port create. And do not let
    the original 'master' (current is backup) host override
    the gateway port binding host.
    
    Closes-Bug: #1793529
    Change-Id: Icb2112c7f0bd42c4f4b1cf32d6b83b6d97f85ef7


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

Title:
  [dvr][ha][dataplane down] router_gateway port binding host goes wrong
  after the 'master' host down/up

Status in neutron:
  Fix Released

Bug description:
  ENV:
  master
  devstack multinode install:
  1 controller node
  2 compute nodes -> dvr_no_external (compute1, compute2)
  2 network nodes -> dvr_snat (network1, network2)

  Problem:
  For L3 DVR HA router, when the network node, which hosting the `master` router, is down and up.
  The router port `device_owner = network:router_gateway` will be binding back to the `down` host.

  How to reproduce:
  1. create DVR_HA router connecting user private network and public external network
  2. create a VM in dvr_no_external compute in private network
  3. create floating IP and associate to the VM port
  4. directly reboot the `master` router located host (network1)

  Some testing output:

  (1) before reboot:
  router `master` is stay in network1
  http://paste.openstack.org/show/730423/
  (2)
  during reboot:
  http://paste.openstack.org/show/730424/

  (3) after reboot:
  router `master` is in network2
  http://paste.openstack.org/show/730422/
  network:router_gateway port is binding back to network1.
  network:router_centralized_snat is normally binding to network2.

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