-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.15.0
-
None
-
No
-
3
-
uShift Sprint 242
-
1
-
False
-
-
MicroShift has changed its name resolution mechanism when using .local hostnames. Previously this was broken because of looking only at /etc/resolv.conf.
-
Bug Fix
-
In Progress
Description of problem:
When using a .local suffix in the hostname MicroShift is unable to retrieve logs from any pod.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
1. Configure a .local hostname 2. Install MicroShift 3. Try to retrieve logs for any pod
Actual results:
# oc logs -n openshift-ingress router-default-f6dc6d4b8-gbltq Error from server: Get "https://microshift-dev.local:10250/containerLogs/openshift-ingress/router-default-f6dc6d4b8-gbltq/router": dial tcp: lookup microshift-dev.local on 192.168.122.1:53: server misbehaving
Expected results:
Actual logs from the pod
Additional info:
- blocks
-
OCPBUGS-19872 mDNS resolution not working when retrieving logs
- Closed
- is cloned by
-
OCPBUGS-19872 mDNS resolution not working when retrieving logs
- Closed
- links to
-
RHEA-2023:7200 Red Hat build of MicroShift 4.15.z bug fix and enhancement update