Bug 2059139

Summary:	No DNS configured on WWAN modem connections
Product:	Red Hat Enterprise Linux 9	Reporter:	Beniamino Galvani <bgalvani>
Component:	NetworkManager	Assignee:	Beniamino Galvani <bgalvani>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	bgalvani, desktop-qa-list, fpokryvk, lrintel, nm-team, rkhan, sukulkar, till, vbenes
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.36.0-2.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2059138	Environment:
Last Closed:	2022-05-17 15:48:29 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:
Bug Depends On:	2059138
Bug Blocks:

Description Beniamino Galvani 2022-02-28 09:57:01 UTC

+++ This bug was initially created as a clone of Bug #2059138 +++

Description of problem:
when connecting via a WWAN modem, the DNS server provided by the network is not written to resolv.conf


Version-Release number of selected component (if applicable):
1.36.0-*


How reproducible:
always


Steps to Reproduce:
activate a modem, check /etc/resolv.conf. Or run this modified NMCI test:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/974/diffs


Additional info:
upstream report:  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/931
upstream MR:      https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1122

Comment 4 errata-xmlrpc 2022-05-17 15:48:29 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 (new packages: NetworkManager), 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-2022:3915