Bug 1370048

Summary:	resolv.conf is getting overwritten by NetworkManager
Product:	[oVirt] vdsm	Reporter:	Fabian Deutsch <fdeutsch>
Component:	Core	Assignee:	Ondřej Svoboda <osvoboda>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.18.11	CC:	bugs, mburman
Target Milestone:	ovirt-4.0.4	Keywords:	TestOnly
Target Release:	4.18.12	Flags:	fdeutsch: ovirt-4.0.z? fdeutsch: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-26 12:37:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1304509

Description Fabian Deutsch 2016-08-25 07:25:54 UTC

Description of problem:
Currently vdsm is handling resolv.conf - but in case that NM is enabled, resolv.conf will be overwritten i-.e. if an interface changes.

This behavior can be disabled in NM by using
[main]
dns=none

The question is if it should be disabled or if vdsm leaves resolv.conf handling to NM.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Kenigsberg 2016-08-27 19:46:41 UTC

the same code fixing bug 1351095 would fix this one, too.

Comment 2 Michael Burman 2016-09-01 09:37:31 UTC

Verified on - 4.0.4-0.1.el7ev and vdsm-4.18.12-1.el7ev.x86_64