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

OpenShift installation on GCP via IPI on existing Subnet is failing because of a private dns zone using the same dns name but not binding to the cluster's VPC

XMLWordPrintable

    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          A similar testing scenario to OCPBUGS-38719, but with the pre-existing dns private zone is not a peering zone, instead it is a normal dns zone which binds to another VPC network. And the installation will fail finally, because the dns record-set "*.apps.<cluster name>.<base domain>" is added to the above dns private zone, rather than the cluster's dns private zone. 

      Version-Release number of selected component (if applicable):

          4.18.0-0.nightly-multi-2024-10-24-093933

      How reproducible:

          Always

      Steps to Reproduce:

          Please refer to the steps told in https://issues.redhat.com/browse/OCPBUGS-38719?focusedId=25944076&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25944076

      Actual results:

          The installation failed, due to the cluster operator "ingress" degraded

      Expected results:

          The installation should succeed.

      Additional info:

          

              rh-ee-bbarbach Brent Barbachem
              rhn-support-jiwei Jianli Wei
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: