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

[4.17] FRR-K8s default hold time and keepalive time different from metallb's one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.18
    • 4.16, 4.17, 4.18
    • Networking / Metal LB
    • None
    • None
    • CNF Network Sprint 259, CNF Network Sprint 260, CNF Network Sprint 262
    • 3
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      The default holdtime of frr-k8s is different from the metallb one. This means that a bgppeer created without specifiying the hold time will conflict with an frrconfiguration created without specifying the hold time.
      
      This does not provide a good user experience as a user will get an error without really understanding what's wrong in his configuration.    

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

          

      How reproducible:

          always

      Steps to Reproduce:

          1. deploy metallb with frr-k8s as backend
          2. create a bgppeer with no hold time
          3. create an frr configuration with the same session details and no hold time
          

      Actual results:

          the webhook intercepts the mismatch

      Expected results:

      both configurations are created    

      Additional info:

          

              obraunsh@redhat.com Ori Braunshtein
              fpaoline@redhat.com Federico Paolinelli
              Arti Sood Arti Sood
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: