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 2008446 - "Failed to find suitable interface for saving DNS name servers" when configuring an unrelated interface
Summary: "Failed to find suitable interface for saving DNS name servers" when configur...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.3
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: 2021-09-28 09:35 UTC by siva kanakala
Modified: 2021-12-07 14:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 14:00:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1939557 1 urgent CLOSED "Failed to find suitable interface for saving DNS name servers" when configuring an unrelated interface 2023-10-04 07:40:57 UTC
Red Hat Issue Tracker RHELPLAN-98334 0 None None None 2021-09-28 09:35:37 UTC

Comment 5 Fernando F. Mancera 2021-09-29 09:21:21 UTC 
As reported on the bug cloned, this was happening because the user configuration was wrong. A strange profile was added to the node and therefore the configuration was not correct. They are investigating where this profile came from but it is not coming from Nmstate.

If this is happening again or some action is required, please open it again.

Thanks,
Fernando.
Comment 6 Fernando F. Mancera 2021-09-29 09:24:19 UTC 
(In reply to Fernando F. Mancera from comment #5)
> As reported on the bug cloned, this was happening because the user
> configuration was wrong. A strange profile was added to the node and
> therefore the configuration was not correct. They are investigating where
> this profile came from but it is not coming from Nmstate.
> 
> If this is happening again or some action is required, please open it again.
> 
> Thanks,
> Fernando.

Please, refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1939557
Comment 7 Fernando F. Mancera 2021-10-04 15:59:47 UTC 
This bug is going to be re-assign to the right component. Petr, could you do that? Thanks!
Comment 9 Gris Ge 2021-10-12 13:02:19 UTC 
Hi Siva,

To support static DNS in nmstate, you need neither:
 1. Interface with static IP and static default gateway(route).
 2. Interface with DHCP/Autoconf enabled with `auto-dns: False`.

In your example, you are missing the default gateway.

Please try to include a route something like:

```
routes:
  config:
  - destination: 0.0.0.0/0
    next-hop-address: 10.28.16.1
    next-hop-interface: ens1f0
```
Comment 14 Quique Llorente 2021-11-03 14:36:13 UTC 
*** Bug 2017623 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.