Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-4845

MetallB ignores NodeNetworkUnavailable condition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.10
    • Networking / Metal LB
    • None
    • None
    • CNF Network Sprint 229, CNF Network Sprint 230, CNF Network Sprint 232, CNF Network Sprint 233, CNF Network Sprint 234, CNF Network Sprint 235, CNF Network Sprint 236, CNF Network Sprint 237, CNF Network Sprint 238, CNF Network Sprint 239
    • 10
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      This is an upstream issue bug report: https://github.com/metallb/metallb/issues/1710
      NodeNetworkUnavailable condition is a Kubernetes node property used to signal whether the node's network is available. MetalLB ignores this condition. As the issue above reports, this behavior can cause an undesired L2 leader election result. 

      Version-Release number of selected component (if applicable):

      RH MetalLB Operator version 4.10.0-202210061437

              lnoy@redhat.com Lior Noy (Inactive)
              lnoy@redhat.com Lior Noy (Inactive)
              Arti Sood Arti Sood
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: