-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.12
-
Critical
-
No
-
Rejected
-
False
-
Description of problem:
Not able to install OCP 4.12 in Azure with custom network/DNS Customer has it's own/existing DNS name used for the installation, Customer has deployed the same using install-config in past[1+ year] with their own IP and DNS.
Version-Release number of selected component (if applicable):
How reproducible:
Install a cluster on 4.12 Azure
Steps to Reproduce:
1. Created install-config.yaml as per the attachment. 2. Try to install OCP 4.12.17 on Azure
Actual results:
Failed to write CNAME Failed to perform 'write' on resource(s) of type 'dnszones/CNAME', because the parent resource '/subscriptions/xxx-xxxx-xxxx-xxxxx-xx/resourceGroups/xxx-xxxx/providers/Microsoft.Network/dnszones/xxxxxx.net' could not be found.\"" Note : We have sanitized the resource group and DNS domain name. Same we can see in the openshift logs.
Expected results:
OCP 4.12 Cluster should be install successfully with custom/existing/external DNS
Additional info:
Some addition Links: Customer is performing the installation for OCP 4.12 using with same install-config but in past OCP 4.8 was able to install using the same install-config.yaml. Attached install-config.yaml and openshift-install.logs for more details: [+] https://drive.google.com/drive/folders/1ctElwWj76VcNeuoXXKN8UouvldASWcMf?usp=sharing [1] https://docs.openshift.com/container-platform/4.9/networking/dns-operator.html#nw-dns-operator-managementState_dns-operator [2] https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html#ocp-4-9-networking-dns-management-state [3] https://docs.openshift.com/container-platform/4.12/installing/installing_azure/installing-azure-customizations.html