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 2177842 - Minimize the impact on existing interface when only desiring DNS config changes
Summary: Minimize the impact on existing interface when only desiring DNS config changes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-13 16:58 UTC by Gris Ge
Modified: 2023-11-07 09:02 UTC (History)
6 users (show)

Fixed In Version: nmstate-2.2.9-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:24:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
verified.log (18.52 KB, text/plain)
2023-05-08 11:33 UTC, Mingyu Shi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github nmstate nmstate pull 2273 0 None open nm dns: Do not use current interface which is unmanaged/external managed 2023-03-15 11:54:50 UTC
Red Hat Issue Tracker NMT-382 0 None None None 2023-03-13 17:00:26 UTC
Red Hat Issue Tracker RHELPLAN-151634 0 None None None 2023-03-13 17:00:30 UTC
Red Hat Product Errata RHBA-2023:6323 0 None None None 2023-11-07 08:24:23 UTC

Description Gris Ge 2023-03-13 16:58:44 UTC 
Description of problem:

Given a system with NM external managed (or unmanaged) interface holding IP stack information.

When nmstate user desiring a DNS config changes.

Then nmstate should not touch any interface.

Version-Release number of selected component (if applicable):
nmstate-2.2.7-1.el9

How reproducible:
100%

Steps to Reproduce:
1. Delete all NM connections in a server or NM
2. Use ip command to set up the IP network on gateway NIC.
3. Apply desire state with DNS config only. e.g.:

```
dns-resolver:
  config:
    search:
      - example.com
    server:
      - 1.1.1.1
      - 8.8.8.8
```

Actual results:

Nmstate crate NM connection for this external managed NIC with DNS stored in.

Expected results:

Nmstate should not create any NM connections but use global DNS to set the DNS configurations.


Additional info:

On next modification of DNS via nmstate, if nmstate found a better place(NM controlled NIC with IP enabled), nmstate should convert this global DNS back to interface based DNS.
Comment 1 Gris Ge 2023-03-15 11:54:50 UTC 
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2273

After patched, nmstate will not use unmanaged interface or external managed interface to store DNS config.
When no interface available for storing DNS, global DNS will be used.

To test unmanaged interface:
 * Use `nmcli d set <if_name> managed false` to mark all interface as unmanaged.
 * Apply a desire state with DNS config only.
 * You should see no NM connection been created.
 * `/var/lib/NetworkManager/NetworkManager-intern.conf` should contain the DNS config.

To test external managed interface:
 * Make sure `NetworkManager-config-server` installed and daemon restarted.
 * Use ip command to create a interface(any type) with IP
 * If interface is marked as unmanaged, run `nmcli d set <if_name> managed true`
 * Use `nmcli d` to confirm the NIC is in the `connected (externally)` state
 * Apply a desire state with DNS config only.
 * You should see no NM connection been created.
 * `/var/lib/NetworkManager/NetworkManager-intern.conf` should contain the DNS config.
Comment 5 Mingyu Shi 2023-05-08 11:33:19 UTC 
Created attachment 1963179 [details]
verified.log

Verified with:
nmstate-2.2.10-3.el9.x86_64
nispor-1.2.10-1.el9.x86_64
NetworkManager-1.43.6-1.el9.x86_64
DISTRO=RHEL-9.3.0-20230504.0
Comment 7 errata-xmlrpc 2023-11-07 08:24:02 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:6323
Note You need to log in before you can comment on or make changes to this bug.