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

[UDN] Incorrect L3 UDN configuration can prevent cluster scale-out

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • None
    • CORENET Sprint 275
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:
      If a Layer3 UserDefinedNetwork exists in the cluster having a configuration that limits the number of nodes when the cluster is expanded or scaled out the nodes not receiving the subnet of that UDN remain in `NotReady` status and the related ovnkube-node pod get into CrashLoopBackOff. In this scenario a project admin has the possibility of break the cluster or make impossible to scale it out.

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

      How reproducible:
      Always

      Steps to Reproduce:

      1. Install a cluster with 6 nodes.

      2. Create L3 P-UDN configuration that can allow 8 nodes.

      3. Expand the cluster to have more than 8 nodes.

      Actual results:
      The 9th and subsequent nodes join the cluster but remain in `NotReady` status and the related ovnkube-node pod get into CrashLoopBackOff.

      Expected results:
      The node should be able to join the cluster and only the UDN should fail.

              sdn-team-bot sdn-team bot
              rhn-support-cpassare Christian Passarelli
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: