-
Bug
-
Resolution: Done
-
Critical
-
4.13.0
-
No
-
5
-
uShift Sprint 233, uShift Sprint 234
-
2
-
False
-
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:
- clones
-
OCPBUGS-10766 MicroShift pods cannot resolve local host name
- Closed
- is blocked by
-
OCPBUGS-10766 MicroShift pods cannot resolve local host name
- Closed
- links to