yahoo-eng-team team mailing list archive

[OpenStack Infra <2097770@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/941283
Committed: https://opendev.org/openstack/neutron/commit/438808f161044d7d2cb25b3a4dc783c181493da4
Submitter: "Zuul (22348)"
Branch:    master

commit 438808f161044d7d2cb25b3a4dc783c181493da4
Author: Rodolfo Alonso <ralonsoh@xxxxxxxxxx>
Date:   Tue Feb 11 17:52:00 2025 +0000

    Revert "Track all interfaces in Keepalived"
    
    This reverts commit bee07defacf61ccef19adbe54677b0a0a00ae65b.
    
    Reason for revert:
    The only interfaces tracked by keepalived are the HA interfaces. The
    fixed IP / floating IPs / routes are linked to the internal router interfaces or the gateway interface, that are interfaces not tracked
    by keepalived. These IP addresses / routes should have the suffix
    "no_track" in the configuration entry.
    
    This is commented in [1], when the keepalived VIP HA configuration
    was fixed, excluding any IP address other than the VIP of the HA interface, that are placed in the "virtual_ipaddress_excluded" and
    belong to no tracked interfaces.
    
    [1]https://github.com/openstack/neutron/blob/ad628353da68dcbf9e6ff25c47fd6753eee22683/neutron/agent/linux/keepalived.py#L271-L281
    
    Change-Id: I4dfd89606042ba545559eb03d47fceee3b0895fc
    Closes-Bug: #2097770


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

Title:
  [ML2/OVS] Detaching floating ip of instances makes Neutron L3 routers
  failover

Status in neutron:
  Fix Released

Bug description:
  When a floating ip of an instance gets detached, the router (L3, in HA
  mode) that the instance uses gets failed-over to different L3 agent
  causing disruption on tenant network.

  Pre-condition:
  Number of VMs: 42
  Number of routers: 44
  User-role: Both member and admin

  Steps to reproduce.

  1. Prepare any network that is connected to external network with any router.
  2. Spawn a VM on the network and assign a floating ip
  3. Prepare monitoring router network agent failover
  e.g. ``watch "openstack network agent list --long --router <router id>"`` (on API reachable node)
  or ``ip netns exec qrouter-<router id> tcpdump -i <ha interface>`` on node where Neutron L3 agent is running.
  4. Detach the floating ip of the VM.

  Expected result: No failover happens to the router
  Actual result: Failover can be observed.

  This bug was reproduce-able from systems on Antelope and Caracal releases that use ML2/OVS.
  Caracal Host OS: 5.14.0-503.16.1.el9_5.x86_64
  Antelope Host OS: 5.14.0-362.13.1.el9_3.x86_64

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