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

Cluster dns-default service periodically reports io timeout after 4.11.35 upgrade

XMLWordPrintable

    • No
    • SDN Sprint 236, SDN Sprint 238, SDN Sprint 239, SDN Sprint 240, SDN Sprint 241, SDN Sprint 242, SDN Sprint 243
    • 7
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Customer Escalated

      Description of problem:

      A cluster upgraded from 4.11.34 to 4.11.35 and has begun experiencing intermittent DNS resolution failures via its dns-default service on 172.30.0.10.

At least half of all DNS resolution attempts via @172.30.0.10 seem to result in an io timeout error.

Restarting all DNS pods does not appear to make any difference. 

Attempting to perform DNS resolution inside the individual dns-default pods (using their host network) is successful. However, any pod attempting to resolve via @172.30.0.10 will periodically fail.

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

      4.11.35

      How reproducible:

      The cluster has been consistently exhibiting DNS failure since it upgraded.

            mkennell@redhat.com Martin Kennelly
            mbargenq Matt Bargenquast (Inactive)
            Anurag Saxena Anurag Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: