yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1497272@xxxxxxxxxxxxxxxxxx>]

It's keepalived issue, and supported platforms like centos/rhel or
xenial, already ship fixed packages. We also documented the issue in
networking guide. There seems to be nothing we can do more on neutron
side, so moving the bug to Won't Fix.

** Changed in: neutron
       Status: Triaged => Won't Fix

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

Title:
  L3 HA: Unstable rescheduling time for keepalived v1.2.7

Status in neutron:
  Won't Fix
Status in openstack-ansible:
  Fix Released
Status in openstack-manuals:
  Fix Released

Bug description:
  I have tested work of L3 HA on environment with 3 controllers and 1 compute (Kilo) with this simple scenario:
  1) ping vm by floating ip
  2) disable master l3-agent (which ha_state is active)
  3) wait for pings to continue and another agent became active
  4) check number of packages that were lost

  My results are  following:
  1) When max_l3_agents_per_router=2, 3 to 4 packages were lost.
  2) When max_l3_agents_per_router=3 or 0 (meaning the router will be scheduled on every agent), 10 to 70 packages were lost.

  I should mention that in both cases there was only one ha router.

  It is expected that less packages will be lost when
  max_l3_agents_per_router=3(0).

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