Bug 2008446

Summary:	"Failed to find suitable interface for saving DNS name servers" when configuring an unrelated interface
Product:	Red Hat Enterprise Linux 8	Reporter:	siva kanakala <skanakal>
Component:	nmstate	Assignee:	Gris Ge <fge>
Status:	CLOSED NOTABUG	QA Contact:	Mingyu Shi <mshi>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	ellorent, ferferna, fge, jiji, jishi, josearod, manrodri, network-qe, phoracek, till, tonyg
Target Milestone:	rc	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-07 14:00:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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. ***