Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-17355

Azure: pre-flight check public DNS zone

XMLWordPrintable

    • Critical
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      We should perform a pre-flight check to ensure that a public DNS zone exists in the baseDomainResourceGroup before beginning the install, otherwise the install will fail late during Terraform resource creation.

      We should only perform this validation when the cluster is set to use the External publish type.

      We have seen this problem crop up in a couple of different bugs. Discussed here and also the original bug, of which this is a clone. I went ahead and closed the original bug because it was attached to a case and there was additional context beyond the validation. I'm opening this bug solely to represent the need to validate the existence of a public DNS zone.

      ===========================

      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 

              jhixson_redhat John Hixson
              rhn-support-nprajapa Nikhil Prajapati
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: