yahoo-eng-team team mailing list archive

[OpenStack Infra <2112110@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/951274
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/4ea86cee1a232801e76665569974c7e668d2e308
Submitter: "Zuul (22348)"
Branch:    master

commit 4ea86cee1a232801e76665569974c7e668d2e308
Author: Fernando Royo <froyo@xxxxxxxxxx>
Date:   Thu May 29 13:44:23 2025 +0200

    Ensure LB with HM rechecks member status after re-enable
    
    This patch fixes an issue where disabling a LoadBalancer member
    sets its status to ERROR instead of OFFLINE.
    
    While in the ERROR state, re-enabling the member does not update
    its status, and the member is not reintegrated into the "vips" field
    of the LoadBalancer row in the OVN NB database. As a result, the
    Health Monitor does not resume its checks on the member.
    
    This patch ensures that re-enabled members are correctly reintegrated
    and that health checks are properly resumed.
    
    Closes-bug: #2112110
    Change-Id: If2ca76df87c0f5a713604212ed6cb77792d0010c


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

Title:
  [ovn-octavia-provider] LoadBalancer member not coming back after
  disable-enable

Status in neutron:
  Fix Released

Bug description:
  The logical over the disable/enable for a member looks not working
  fine if a HM is checking the pool where member is attached. If you
  disable a backend member and put it enable again it is not comming as
  a available backend member to redirect LB traffic:

  Step to reproduce the issue.
  1. Create a Load Balancer with:
     A listener on port 80 using TCP protocol
     A pool with a HM attached
  2. Add a VM (which is Active) to the pool as a member:
     The load balancer works correctly
     HM reports correctly the status as ONLINE
  3. Disable the member
     HM reports  the status as ERROR, where OFFLINE looks more appropiate
  4. Enable the member
     HM doesn't detect the change and mantain the ERROR status not checking again the probes to the member so  movin to ONLINE, also vips field keeps {} (empty)

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