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

[Baremetal] [Agent] Allow machine CIDR to be empty when having a Dual-stack cluster and userManagedNetworking: true

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • None
    • AI-34
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      We can deploy a ipv4 only cluster just fine, but when we enable a dual-stack cluster we get this error:
      error: Reason: Dual-stack cluster cannot be created with empty Machine Networks
      https://github.com/openshift/assisted-service/blob/master/internal/cluster/validations/validations.go#L776
      
      We have an external loadbalancer for our ingress & API traffic which is on subnet 10.123.127.0/24
      Our machinecidr range is on 10.124.0.0/24.
      
      When specifying userManagedNetworking: true it should not check if the machine CIDR range is not specified even for dual-stack clusters.
      
      I cannot specify the machine CIDR range because then I get this error: No suitable matching CIDR found for VIP. It expects the Ingress / API VIP to be in the machine CIDR range which is not in our case.
      
      https://github.com/openshift/assisted-service/blob/master/internal/network/machine_network_cidr.go#L73
      
      So to summarise:
      1. Allow not defined machine cidr range for dual-stack clusters as well.
      2. OR allow Ingress/API vip outside of machine cidr range.

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

      4.13.z

      How reproducible:

      100%

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

      1. Allow not defined machine cidr range for dual-stack clusters as well. 2. OR allow Ingress/API vip outside of machine cidr range.

      Additional info:

      This is a blocker for my customer since they cannot deploy a dual-stack cluster because of that issue

              beth.white Beth White
              rhn-support-andbartl Andy Bartlett
              None
              None
              Lital Alon Lital Alon
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: