A majority of Single Node OpenShift (SNO) deployments need to support IPv6 in their deployments and due to that customers should be allowed to only specify OVNKubernetes as the NetworkType in the install-configs. The current default networkType for SNO deployments is OpenShiftSDN. So, we also need to change the default just for this deployment type (for now) to OVNKubernetes. Thanks for opening a bug report! Before hitting the button, please fill in as much of the template below as you can. If you leave out information, it's harder to help you. Be ready for follow-up questions, and please respond in a timely manner. If we can't reproduce a bug we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. Version: 4.11 $ openshift-install version <your output here> Platform: #Please specify the platform type: aws, libvirt, openstack or baremetal etc. Please specify: * IPI (automated install with `openshift-install`. If you don't know, then it's IPI) * UPI (semi-manual installation on customized infrastructure) What happened? #Enter text here. #See the troubleshooting documentation (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md) for ideas about what information to collect. #For example, # If the installer fails to create resources (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-create-resources), attach the relevant portions of your `.openshift_install.log.` # If the installer fails to bootstrap the cluster (https://github.com/openshift/installer/blob/master/docs/user/troubleshootingbootstrap.md), attach the bootstrap log bundle. # If the installer fails to complete installation after bootstrapping completes (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-initialize-the-cluster), attach the must-gather log bundle using `oc adm must-gather` # Always at least include the `.openshift_install.log` What did you expect to happen? #Enter text here. How to reproduce it (as minimally and precisely as possible)? $ your-commands-here Anything else we need to know? #Enter text here.
Had a check with ./openshift-install 4.11.0-0.nightly-2022-07-13-131410 The explanation of networkType has been updated as following: # ./openshift-install explain installconfig.networking.networkType KIND: InstallConfig VERSION: v1 RESOURCE: <string> NetworkType is the type of network to install. The default value is OVNKubernetes for Single Node OpenShift and OpenShiftSDN for all other platforms. When no networkType set in install-config.yaml, creating manifests for the SNO cluster, the networkType was set to OVNKubernetes by default: # grep networkType * cluster-config.yaml: networkType: OVNKubernetes cluster-network-01-crd.yml: networkType: cluster-network-01-crd.yml: networkType: cluster-network-01-crd.yml: networkType: cluster-network-02-config.yml: networkType: OVNKubernetes When setting networkType to OpenShiftSDN for the SNO cluster, it will fail as following: 07-14 11:08:45.922 [INFO] Generating manifests files..... 07-14 11:08:45.922 level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: networking.networkType: Invalid value: "OpenShiftSDN": networkType OpenShiftSDN is currently not supported on Single Node OpenShift
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069