-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19, 4.20
-
None
-
None
-
False
-
-
None
-
None
-
None
-
Unspecified
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Installing OCP on Azure using openshift-installer fails for me in specific regions: eastus2 and westus3 with the following error:
\\n \\\"error\\\": {\\n \\\"code\\\": \\\"InvalidAvailabilityZone\\\",\\n \\\"message\\\": \\\"The zone(s) '4' for resource 'Microsoft.Network/publicIPAddresses/pip-caas-bdatt-1849-pool-kqm28-controlplane-outbound' is not supported. The supported zones for location 'eastus2' are '1,2,3'\\\"\\n }\\n}\
I tried Single Node Openshift + FIPS enabled, and 3-nodes non-FIPS, both 4.19 and 4.20
I tried provisioning in regions westus and centralus as well, it worked.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Trigger provisioning of OCP on Azure in region eastus2 or westus3
2.
3.
Actual results:
Failed to provision
Expected results:
Successful provisioned
Additional info:
- I didn't try with other versions different from [4.19, 4.20], other regions different from [eastus2, westus3, westus, centralus] - we have always used eastus2 and westus3 as regions for our Azure clusters, without issues. Hence this might be due to some new changes in Azure cloud or OCP installer?
