Bug 1622533 – PEERDNS=no does not avoid to updating /etc/resolv.conf [rhel-7.5.z]

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1622533 - PEERDNS=no does not avoid to updating /etc/resolv.conf [rhel-7.5.z]

Summary:	PEERDNS=no does not avoid to updating /etc/resolv.conf [rhel-7.5.z]

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	initscripts (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	All Linux

Priority	urgent Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	David Kaspar [Dee'Kej]
QA Contact:	Daniel Rusek
Docs Contact:	Mirek Jahoda

URL:
Whiteboard:
Keywords:	Patch, Regression, Reproducer, ZStream

Depends On:	1610411
Blocks:
	Show dependency tree / graph

Reported:	2018-08-27 08:16 EDT by Jaroslav Reznik
Modified:	2018-09-25 15:10 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	initscripts-9.49.41-1.el7_5.2
Doc Type:	Bug Fix
Doc Text:	Previously, a condition for handling the RESOLV_MODS option was not set correctly. As a consequence, the /etc/resolv.conf could be updated even if the PEERDNS option was set to "no". With this update, the condition has been fixed, and "PEERDNS=no" is no longer ignored.
Story Points:	---
Clone Of:	1610411
Environment:
Last Closed:	2018-09-25 15:10:45 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:2764	None	None	None	2018-09-25 15:10 EDT

Groups: None (edit)

Description Jaroslav Reznik 2018-08-27 08:16:37 EDT

This bug has been copied from bug #1610411 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 7 errata-xmlrpc 2018-09-25 15:10:45 EDT

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, 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-2018:2764

Note You need to log in before you can comment on or make changes to this bug.