Description of problem:
- While deploying a private OpenShift cluster on top of Azure via IPI mode of installation for version 4.17, the process fails with the below error message :- ~~~ time="2024-10-21T07:38:08Z" level=fatal msg="failed to fetch Cluster: failed to fetch dependency of \"Cluster\": failed to generate asset \"Cluster API Manifests\": failed to generate Azure manifests: failed to get azure ip availability: network.VirtualNetworksClient#CheckIPAddressAvailability: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code=\"PrivateIPAddressNotInAnySubnet\" Message=\"Private static IP address 10.0.0.100 does not belong to the range of any subnet in the virtual network /subscriptions/<subscription_id>/resourceGroups/<nsg_name>/providers/Microsoft.Network/virtualNetworks/<nw_name>\" Details=[]" ~~~ - The install-config.yaml being used for the deployment looks like this :- ~~~ apiVersion: v1 baseDomain: <base_domain> controlPlane: hyperthreading: Enabled name: master platform: azure: osDisk: diskSizeGB: 128 diskType: Premium_LRS type: Standard_D8ls_v5 replicas: 1 compute: - architecture: amd64 hyperthreading: Enabled name: worker platform: azure: osDisk: diskSizeGB: 128 diskType: Premium_LRS type: Standard_D4as_v5 zones: - "1" - "2" - "3" replicas: 0 metadata: name: <name> networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineNetwork: - cidr: ...REDACTED... networkType: OVNKubernetes serviceNetwork: - 172.30.0.0/16 platform: azure: baseDomainResourceGroupName: <RSG_name> cloudName: <cloud_name> outboundType: UserDefinedRouting region: <region> networkResourceGroupName: <nsg_name> virtualNetwork: <nw_name> controlPlaneSubnet: <subnet_name_control-plane> computeSubnet: <subnet_name_compute> resourceGroupName: <RSG_name> publish: "Internal" pullSecret: '{<removed>}' sshKey: ssh-rsa AAAAB3Nza..... ~~~ - The issue here is, the same install-config works with OpenShift 4.16 version, but not with OpenShift 4.17
Version-Release number of selected component (if applicable):
4.17.z
Actual results:
The installation fails for 4.17, but completes in case of 4.16
Expected results:
Should work with 4.17 as well.
Additional info: