-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15.0
-
None
-
Important
-
No
-
3
-
uShift Sprint 242, Plumbing Sprint 251
-
2
-
Rejected
-
False
-
Description of problem:
If a host is using systemd-resolved, the microshift DNS pod keeps failing with error: plugin/forward: not an IP address or file: "/run/systemd/resolve/resolv.conf"
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. dnf install -y systemd-resolved 2. systemctl enable systemd-resolved 3. systemctl start microshift
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-19363 systemd-resolved breaks microshift DNS pod
- Closed
- depends on
-
OCPBUGS-19363 systemd-resolved breaks microshift DNS pod
- Closed
- links to
-
RHBA-2023:7684 Red Hat build of MicroShift 4.14.z bug fix and enhancement update