Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-20743

LoadBalancer member not coming back after disable-enable

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • python-ovn-octavia-provider-4.0.3-18.0.20251010114653.393b8bd.el9osttrunk
    • python-ovn-octavia-provider-4.0.3-18.0.20251010114653.393b8bd.el9osttrunk
    • rhos-connectivity-vans
    • None
    • Hide
      .Fixes load-balancer member re-enablement behavior

      Before this update, disabled load-balancer members remained in an `ERROR` state even after being re-enabled, causing incorrect load balancer status reporting and potential traffic distribution issues. This problem was caused by the health monitor incorrectly reporting the disabled member status as `ERROR` instead of `OFFLINE`. This incorrect status prevented the disabled member from transitioning back to `ONLINE` when it was re-enabled.
      With this update, the health monitor correctly sets the disabled member status to `OFFLINE` and the problem has been resolved. Disabled members are now correctly marked as `OFFLINE` and the members automatically transition back to `ONLINE` when they are re-enabled.
      Show
      .Fixes load-balancer member re-enablement behavior Before this update, disabled load-balancer members remained in an `ERROR` state even after being re-enabled, causing incorrect load balancer status reporting and potential traffic distribution issues. This problem was caused by the health monitor incorrectly reporting the disabled member status as `ERROR` instead of `OFFLINE`. This incorrect status prevented the disabled member from transitioning back to `ONLINE` when it was re-enabled. With this update, the health monitor correctly sets the disabled member status to `OFFLINE` and the problem has been resolved. Disabled members are now correctly marked as `OFFLINE` and the members automatically transition back to `ONLINE` when they are re-enabled.
    • Bug Fix
    • Done
    • Moderate

      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)

       

              ashtempl Arkady Shtempler
              froyo@redhat.com Fernando Royo
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: