Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 86476

Summary: redhat-network-config does not change dns search path when profile changed
Product: [Retired] Red Hat Linux Reporter: Joshua Legbandt <jtlegbandt>
Component: redhat-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-08-11 14:10:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joshua Legbandt 2003-03-23 17:27:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; 7.1) Gecko/20030313

Description of problem:
When changing from a profile with values in the DNS Search Path to a profile
with an empty DNS Search Path the previous search path is kept.

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

How reproducible:

Steps to Reproduce:
1. Load a profile with a DNS Search Path
2. Change to a profile with an empty DNS Search Path
3. See the DNS Search Path not change

Actual Results:  DNS Search Path retains the dns search path of the previous profile

Expected Results:  DNS Search Path becomes empty

Additional info:

Comment 2 Harald Hoyer 2003-08-11 14:10:24 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.