Version:

$ openshift-install version
openshift-install unreleased-master-6048-gbdab9b334f23f2ef1f277fced734f209d7840ae6
built from commit bdab9b334f23f2ef1f277fced734f209d7840ae6
release image registry.ci.openshift.org/origin/release:4.11
release architecture amd64

Platform: azure

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)

What happened?

The UltraSSD validation implemented in CORS-1991 [1] will only accept instances if they are in single-zone regions. Even then, the machine-api-provider-azure will create Availability Sets which is incompatible with UltraSSD. In order to correctly validate for ultrassds in multi-zone regions we need to check the zoneDetails in the location info. 

[1] https://issues.redhat.com/browse/CORS-1991
 

What did you expect to happen?

The Instance types are correctly validated based on whether ultrassd is available in a given region. We need to account for how to deal with the situation where ultrassd is not available in all of the zones in the region. Perhaps in those situations we require users to specify their zones in the install config.


How to reproduce it (as minimally and precisely as possible)?

* Enable ultraSSDCapability in a region with Availability Zones support:

cat > "${cluster_dir}"/install-config.yaml << EOF
apiVersion: v1
baseDomain: ${domain}.openshift.com
metadata:
  name: ${cluster_name}
platform:
  azure:
    baseDomainResourceGroupName: ${rg_name}
    cloudName: AzurePublicCloud
    region: centralus
controlPlane:
  platform:
    azure:
      type: Standard_D8s_v3
      ultraSSDCapability: Enabled

* Deploy the cluster

Anything else we need to know?

#Enter text here.