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

MicroShift pods cannot resolve local host name

XMLWordPrintable

    • No
    • 5
    • uShift Sprint 233, uShift Sprint 234
    • 2
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: Using a .local suffix for hostname breaks name resolution with DNS.
      *Consequence*: MicroShift is unable to reach its own host name.
      *Fix*: Fix mDNS and try to use IPs instead of hostnames where possible.
      *Result*: Bug doesn’t present anymore.
      Show
      *Cause*: Using a .local suffix for hostname breaks name resolution with DNS. *Consequence*: MicroShift is unable to reach its own host name. *Fix*: Fix mDNS and try to use IPs instead of hostnames where possible. *Result*: Bug doesn’t present anymore.
    • Bug Fix

      Description of problem:

      Local host name is not resolved correctly after MicroShift starts

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

      4.13 / 4.14

      How reproducible:

      100%

      Steps to Reproduce:

      1. Start microshift service
2. ping -4 -c 1 `hostname`
3. Run `oc logs` on a pod

      Actual results:

      Host name is incorrectly resolved to 169.254.169.2 IP
Pod logs return the following error
Error from server: Get "https://microshift-dev-rhel9.local:10250/containerLogs/openshift-ingress/router-default-6974d687-d9lxm/router": dial tcp: lookup microshift-dev-rhel9.local on 192.168.122.1:53: no such host

      Expected results:

      Proper host name resolution

      Additional info:

       

              pliurh Peng Liu
              rh-ee-ckyal Chirag Kyal
              Douglas Hensel Douglas Hensel
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: