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

fail to create RHV IPI cluster as apiVIP and ingressVIP are not in machine networks

XMLWordPrintable

    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Customer Escalated

      Description of problem:

      fail to create RHV 4.13.0-rc.7 IPI cluster as apiVIP and ingressVIP are not in machine networks
      
      # ./openshift-install create install-config --dir test
      ? SSH Public Key /root/.ssh/id_rsa.pub
      ? Platform ovirt
      ? Cluster TestEnvironmentCluster
      ? Storage domain 0pnq2-test-vm-storage8
      ? Network ovirtmgmt
      ? VNIC Profile ovirtmgmt
      X Sorry, your reply was invalid: IP expected to be in one of the machine networks: 10.0.0.0/16
      ? Internal API virtual IP [? for help] 192.168.1.10
      
      
      As the user could not define cidr for machineNetwork when creating the cluster or install-config file interactively, it will use default value 10.0.0.0/16, so fail to create the cluster ot install-config when inputting apiVIP and ingressVIP outside of default machinenNetwork.
      
      This was already reported for vSphere and Nutanix here: https://issues.redhat.com/browse/OCPBUGS-7015 
      
      However it seems that the RHV platform is also affected by this issue. 

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

      # ./openshift-install version
      ./openshift-install 4.13.0-rc.7
      built from commit 3e0b2a2ec26d9ffcca34b361896418499ad9d603
      release image quay.io/openshift-release-dev/ocp-release@sha256:aae5131ec824c301c11d0bf11d81b3996a222be8b49ce4716e9d464229a2f92b
      release architecture amd64
      

      How reproducible:

      Always

      Steps to Reproduce:

      1. create install-config.yaml file by running command "./openshift-install create install-config --dir ipi"
      2. failed with above error
      

      Actual results:

      fail to create install-config.yaml file

      Expected results:

      succeed to create install-config.yaml file

      Additional info:

       The current workaround is to use dummy VIPs from 10.0.0.0/16 machinenetwork to create the install-config first and then modify the machinenetwork and VIPs as per your requirement which is overhead and creates a negative experience. 

              padillon Patrick Dillon
              rhn-support-asadawar Abhijeet Sadawarte
              Wenxin Wei Wenxin Wei
              Patrick Dillon
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: