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

[GWAPI] dns_controller error "failed to publish DNS record to zone" (gcp)

    XMLWordPrintable

Details

    • Important
    • Sprint 234, Sprint 235, Sprint 236, Sprint 237, Sprint 238, Sprint 239, Sprint 240
    • 7
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when configuring DNS for Gateway API gateways, the Ingress Operator would attempt to create a DNS record for a gateway listener, even if the listener specified a hostname with a domain that was outside of the cluster's base domain. Consequently, the Ingress Operator attempted, and failed, to publish DNS records, and would return the following error: `failed to publish DNS record to zone`.
      +
      With this update, when creating a `DNSRecord` custom resource (CR) for a gateway listener, the Ingress Operator now sets the `DNSRecord's` DNS management policy to `Unmanaged` if its domain is outside of the cluster's base domain. As a result, the Ingress Operator no longer attempts to publish records, and no longer logs the `failed to publish DNS record to zone` error. (link:https://issues.redhat.com/browse/OCPBUGS-10875[*OCPBUGS-10875*])
      Show
      * Previously, when configuring DNS for Gateway API gateways, the Ingress Operator would attempt to create a DNS record for a gateway listener, even if the listener specified a hostname with a domain that was outside of the cluster's base domain. Consequently, the Ingress Operator attempted, and failed, to publish DNS records, and would return the following error: `failed to publish DNS record to zone`. + With this update, when creating a `DNSRecord` custom resource (CR) for a gateway listener, the Ingress Operator now sets the `DNSRecord's` DNS management policy to `Unmanaged` if its domain is outside of the cluster's base domain. As a result, the Ingress Operator no longer attempts to publish records, and no longer logs the `failed to publish DNS record to zone` error. (link: https://issues.redhat.com/browse/OCPBUGS-10875 [* OCPBUGS-10875 *])
    • Bug Fix
    • Done

    Description

      Description of problem:

      Error message seen during testing:
      2023-03-23T22:33:02.507Z	ERROR	operator.dns_controller	dns/controller.go:348	failed to publish DNS record to zone	{"record": {"dnsName":"*.example.com","targets":["34.67.189.132"],"recordType":"A","recordTTL":30,"dnsManagementPolicy":"Managed"}, "dnszone": {"id":"ci-ln-95xvtb2-72292-9jj4w-private-zone"}, "error": "googleapi: Error 400: Invalid value for 'entity.change.additions[*.example.com][A].name': '*.example.com', invalid"}
      

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

      4.13
      

      How reproducible:

      
      

      Steps to Reproduce:

      1. Setup 4.13 gcp cluster, install OSSM using http://pastebin.test.redhat.com/1092754
      2. Run gateway api e2e against cluster (or create gateway with listener hostname *.example.com)
      3. Check ingress operator logs
      

      Actual results:

      DNS record not published, and continous error in log
      

      Expected results:

      Should publish DNS record to zone without errors
      

      Additional info:

      Miciah: The controller should check ManageDNSForDomain when calling EnsureDNSRecord.  
      

      Attachments

        Activity

          People

            mmasters1@redhat.com Miciah Masters
            cholman@redhat.com Candace Holman
            Hongan Li Hongan Li
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: