RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2059655 - Allowing arbitrary static DNS configuration
Summary: Allowing arbitrary static DNS configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 9.2
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On: 2060905 2073512
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-01 16:13 UTC by Gris Ge
Modified: 2023-10-15 10:52 UTC (History)
7 users (show)

Fixed In Version: nmstate-2.2.5-1.el9
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 07:30:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github nmstate nmstate pull 2198 0 None open nm dns: Support arbitrary DNS config 2023-01-18 10:42:59 UTC
Red Hat Issue Tracker NMT-185 0 None None None 2023-01-26 11:05:11 UTC
Red Hat Issue Tracker RHELPLAN-114138 0 None None None 2022-03-01 16:18:00 UTC
Red Hat Product Errata RHBA-2023:2190 0 None None None 2023-05-09 07:31:13 UTC

Description Gris Ge 2022-03-01 16:13:59 UTC 
Description of problem:

Currently, nmstate has limitation on DNS configuration:
https://nmstate.io/devel/api.html#dns-client-configuration

which require user to defined auto-dns:false or static gateway.

This has been cause a lot problem of CNV:

https://bugzilla.redhat.com/show_bug.cgi?id=2049949
https://bugzilla.redhat.com/show_bug.cgi?id=1939557
https://bugzilla.redhat.com/show_bug.cgi?id=1926143


Version-Release number of selected component (if applicable):
nmstate-1.2.1-1.el8

How reproducible:
100%

Steps to Reproduce:
1. Changed the static DNS configuration without static gateway or auto-dns: false.
2.
3.

Actual results:

Nmstate complaining about not find suitable interface for static DNS.


Expected results:

Nmstate apply the static DNS to /etc/resolv.conf as desired.

Additional info:
Comment 1 Mingyu Shi 2022-03-03 09:44:05 UTC 
Hi Gris, 

I have 2 questions:
1. Where does nmstate store the DNS in? If still stores in an NM connection:
2. Will nmstate set auto-dns to false if DHCP is enabled?

Thank you
Comment 2 Gris Ge 2022-03-04 13:48:31 UTC 
Hi Mingyu,

NetworkManager will support loopback interface, in its connection, we can define DNS as loopback interface always has IP enabled.
We just set the loopback connection with highest DNS priority, so other connection's DNS will append after the loopback/global one.
Comment 4 Gris Ge 2022-06-21 04:29:52 UTC 
Hi Petr,

Can I change this RFE to 9.1 or 9.2?
Comment 5 Petr Horáček 2022-06-21 11:29:10 UTC 
Absolutely. We won't be consuming 9.1.
Comment 9 Gris Ge 2023-01-18 10:43:00 UTC 
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2198


With this patch, we are using NetworkManager global DNS API as fallback method to
apply the desired DNS servers. When storing DNS to NetworkManager via global dns API, 
this will cause _all__ interface level DNS settings been ignored.

This will not be used for `gen_conf` mode. User still get error when not
able to store DNS into interface profile


To test this, you may use this YAML which was not supported before this patch:

```yml
---
dns-resolver:
  config:
    search:
    - example.com
    - example.org
    server:
    - 2001:4860:4860::8888
    - 8.8.8.8
    - 2606:4700:4700::1111
    - 8.8.4.4
```

Unlike DNS stored in interface profile, this DNS configuration is stored at /var/lib/NetworkManager/NetworkManager-intern.conf

Of course, when you change DNS which could be stored in interface, nmstate will purge global DNS config and
use iface profile instead.
Comment 13 Mingyu Shi 2023-02-13 07:48:33 UTC 
Verified with:
nmstate-2.2.5-1.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.90-1.el9.x86_64
Comment 15 errata-xmlrpc 2023-05-09 07:30:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2190
Note You need to log in before you can comment on or make changes to this bug.