yahoo-eng-team team mailing list archive

[OpenStack Infra <1798475@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/627285
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5b7d444b3176dd3f8bf166d332781ac93670a51d
Submitter: Zuul
Branch:    master

commit 5b7d444b3176dd3f8bf166d332781ac93670a51d
Author: LIU Yulong <i@xxxxxxxxxxxx>
Date:   Tue Dec 25 17:45:05 2018 +0800

    Not set the HA port down at regular l3-agent restart
    
    If l3-agent was restarted by a regular action, such as config change,
    package upgrade, manually service restart etc. We should not set the
    HA port down during such scenarios. Unless the physical host was
    rebooted, aka the VRRP processes were all terminated.
    
    This patch adds a new RPC call during l3 agent init, it will try to
    retrieve the HA router count first. And then compare the VRRP process
    (keepalived) count and 'neutron-keepalived-state-change' count
    with the hosting router count. If the count matches, then that
    set HA port to 'DOWN' state action will not be triggered anymore.
    
    Closes-Bug: #1798475
    Change-Id: I5e2bb64df0aaab11a640a798963372c8d91a06a8


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

Title:
  Fullstack test test_ha_router_restart_agents_no_packet_lost failing

Status in neutron:
  Fix Released

Bug description:
  Found at least 4 times recently:

  http://logs.openstack.org/97/602497/5/gate/neutron-fullstack/b8ba2f9/logs/testr_results.html.gz
  http://logs.openstack.org/90/610190/2/gate/neutron-fullstack/1f633ed/logs/testr_results.html.gz
  http://logs.openstack.org/52/608052/1/gate/neutron-fullstack/6d36706/logs/testr_results.html.gz
  http://logs.openstack.org/48/609748/1/gate/neutron-fullstack/f74a133/logs/testr_results.html.gz

  
  Looks that sometimes during L3 agent restart there is some packets loss noticed and that cause failure. We need to investigate that.

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