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

[GWAPI] [4.13.z] The DNS provider failed to ensure the record, invalid value for name (gcp)

XMLWordPrintable

    • Critical
    • No
    • 1
    • Sprint 238
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previosly, the Gateway API feature did not provide DNS records with a trailing dot for the Gateway domain. This caused the status of the DNS record to never become available on the GCP platform. With this update, the DNS records for Gateway API Gateways are properly provisioned and the Gateway API feature works on GCP because the gateway service dns controller now adds a trailing dot if it is missing in the domain. (link:https://issues.redhat.com/browse/OCPBUGS-15434[*OCPBUGS-15434*])

      Cause: The Gateway API feature provides DNS records for Gateways, but neglected to terminate the Gateway domain with a trailing dot. The trailing dot is required by the GCP DNS provisioning, so DNS provisioning for Gateway DNS records failed on the GCP platform.

      Consequence: The status on the DNS record never became available and the DNS name did not resolve on the GCP platform. The Gateway feature was therefore broken on GCP.

      Fix: The gateway service dns controller now adds a trailing dot if it is missing from the domain.

      Result: The DNS records for Gateway API Gateways are properly provisioned and the Gateway API feature works on GCP.
      Show
      * Previosly, the Gateway API feature did not provide DNS records with a trailing dot for the Gateway domain. This caused the status of the DNS record to never become available on the GCP platform. With this update, the DNS records for Gateway API Gateways are properly provisioned and the Gateway API feature works on GCP because the gateway service dns controller now adds a trailing dot if it is missing in the domain. (link: https://issues.redhat.com/browse/OCPBUGS-15434 [* OCPBUGS-15434 *]) Cause: The Gateway API feature provides DNS records for Gateways, but neglected to terminate the Gateway domain with a trailing dot. The trailing dot is required by the GCP DNS provisioning, so DNS provisioning for Gateway DNS records failed on the GCP platform. Consequence: The status on the DNS record never became available and the DNS name did not resolve on the GCP platform. The Gateway feature was therefore broken on GCP. Fix: The gateway service dns controller now adds a trailing dot if it is missing from the domain. Result: The DNS records for Gateway API Gateways are properly provisioned and the Gateway API feature works on GCP.
    • Done

      This is a clone of issue OCPBUGS-15100. The following is the description of the original issue:
      —
      Description of problem:

      Running through instructions for a smoke test on 4.14, the DNS record is incorrectly created for the Gateway.  It is missing a trailing dot in the dnsName.

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

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1.Run through the steps in https://github.com/openshift/network-edge-tools/blob/2fd044d110eb737c94c8b86ea878a130cae0d03e/docs/blogs/EnhancedDevPreviewGatewayAPI/GettingStarted.md until the step "oc get dnsrecord -n openshift-ingress"
2. Check the status of the DNS record: "oc get dnsrecord xxx -n openshift-ingress -ojson | jq .status.zones[].conditions"

       

      Actual results:

      The status shows error conditions with a message like 'The DNS provider failed to ensure the record: googleapi: Error 400: Invalid value for ''entity.change.additions[*.gwapi.apps.ci-ln-3vxsgxb-72292.origin-ci-int-gce.dev.rhcloud.com][A].name'': ''*.gwapi.apps.ci-ln-3vxsgxb-72292.origin-ci-int-gce.dev.rhcloud.com'', invalid'

      Expected results:

      The status of the DNS record should show a successful publishing of the record.

      Additional info:

      Backport to 4.13.z

              cholman@redhat.com Candace Holman
              openshift-crt-jira-prow OpenShift Prow Bot
              Hongan Li Hongan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: