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

Application running in OpenShift failed to resolve Ingress sharding FQDN during the upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.14.z, 4.15.z
    • Networking / DNS
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • Production
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Fastweb has an application, called gateway-v4, that acts as an access point, allowing the user to access this pod and then from there access the other application pods. 
      This gateway appliation contacts the other pods using the fqdn of the sharded routes.
      From what I understand by analyzing the must-gather, the gateway pod asks the default-dns for the resolution of the sharded FQDN which in turn forwards the call to the coredns (openshift-vsphere-infra) which asks one of the two external DNSs for resolution.
      During the upgrade, specifically whenever a master node restarts, the gateway pod receives an NXDOMAIN generating disservice.

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

          

      How reproducible:

      This happened during all the upgrades    

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              nid-team-bot NID Team Bot
              dnessill@redhat.com Daniele Nessilli
              None
              None
              Hongan Li Hongan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: