-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-10.0
-
None
-
anaconda-40.22.3.26-1.el10_0
-
No
-
Critical
-
rhel-anaconda
-
28
-
29
-
1
-
False
-
False
-
-
No
-
None
-
Approved Blocker
-
Pass
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Anaconda copies /run/NetworkManager/conf.d/16-global-dns.conf to the installed system (see PR 6117), but not the other one: /run/NetworkManager/conf.d/16-dns-backend.conf.
What is the impact of this issue to you?
Encrypted DNS is not properly configured and functional on the installed system.
Please provide the package NVR for which the bug is seen:
anaconda-40.22.3.25-1.el10
How reproducible is this bug?:
Always
Steps to reproduce
- Run an installation with the following boot arguments:
ip=192.168.122.10::192.168.122.1:24:client:enp1s0:none rd.net.dns=dns+tls://1.1.1.1#one.one.one.one rd.net.dns-backend=dnsconfd rd.net.dns-resolve-mode=exclusive
- Complete the installation and check if both 16-global-dns.conf and 16-dns-backend.conf exist in /etc/NetworkManager/conf.d/ on the installed system.
Expected results
yes
Actual results
no
- is cloned by
-
RHEL-80233 [RHEL-9] 16-dns-backend.conf is not passed to installed system
-
- Closed
-
- links to
-
RHBA-2024:139695 anaconda bug fix and enhancement update