This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2232578 - dns-resolver option doesn't apply with "Bug: Manager(UnknownDevice)" error
Summary: dns-resolver option doesn't apply with "Bug: Manager(UnknownDevice)" error
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 12:59 UTC by Mat Kowalski
Modified: 2023-08-21 09:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-21 09:43:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-832 0 None None None 2023-08-17 13:25:07 UTC
Red Hat Issue Tracker OCPBUGS-17689 0 None None None 2023-08-17 13:01:12 UTC
Red Hat Issue Tracker   RHEL-1468 0 None None None 2023-08-21 09:43:21 UTC
Red Hat Issue Tracker RHELPLAN-165977 0 None None None 2023-08-17 13:01:41 UTC

Description Mat Kowalski 2023-08-17 12:59:36 UTC 
The following nmstate configuration does not apply even though it's expected it should

```
  desiredState:
    dns-resolver:
      config:
        search:
        - test.com
        server:
        - fd2e:6f44:5dd8:c956::1
        - 2099::9999
    interfaces:
    - name: enp1s0
      type: ethernet
      state: up
      ipv4:
        auto-dns: false
        dhcp: false
        enabled: false
      ipv6:
        auto-dns: false
        dhcp: false
        enabled: false
```

After removing the `dns-resolver` section we get a config that applies correctly, i.e.

```
  desiredState:
    interfaces:
    - name: enp1s0
      type: ethernet
      state: up
      ipv4:
        auto-dns: false
        dhcp: false
        enabled: false
      ipv6:
        auto-dns: false
        dhcp: false
        enabled: false
```

The config with only dns-resolver also does not apply

```
  desiredState:
    dns-resolver:
      config:
        search:
        - test.com
        server:
        - fd2e:6f44:5dd8:c956::1
        - 2099::9999
```

All this definitely points towards dns-resolver section as the one at fault. In all the scenarios when we fail, the error returned is

```
nmstate::nm::query_apply::profile] Got activation failure Bug: Manager(UnknownDevice): No suitable device found for this connection (device [...] not available because profile is not compatible with device (mismatching interface name)).
```

with interface name in the error message being not necessarily the one that we configure (because with only dns-resolver section we don't configure any interface explicitly).

This is a regression because in the current form we have no way of using nmstate to configure DNS. Because of this, we do need a backport to RHEL 9.2 z-stream
Comment 1 Gris Ge 2023-08-17 13:12:53 UTC 
To reproduce this problem, you need system with IP disabled on all interfaces.

Create a OVS bridge with geneve interface type with command:

sudo ovs-vsctl add-port br0 gen0 -- set interface gen0 type=geneve options:remote_ip=192.168.56.12 options:key=123

Afterwards, assign IPv6 address to interface `genev_sys_6081` using `ip` command.

Finally, try to change DNS with IPv6 nameserver.

Expected behavior should be:
 * The `genev_sys_6081` should be marked as `state: ignore`.
 * The DNS is stored as global DNS.

Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2398
Comment 4 RHEL Program Management 2023-08-17 13:56:23 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Note You need to log in before you can comment on or make changes to this bug.