Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1516861

Summary: [DNS] dns servers can only be replaced, not removed
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dan Kenigsberg <danken>
Status: CLOSED DEFERRED QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs
Target Milestone: ---Flags: sbonazzo: ovirt-4.3-
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: 2018-08-01 11:55:33 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:
Attachments:
Description Flags
Logs
none
screenshot none

Description Michael Burman 2017-11-23 12:58:41 UTC
Created attachment 1358205 [details]
Logs

Description of problem:
[DNS] - User defined dns severs should be absolute.

If host was added with 3 name servers in the resolv.conf and the user set 1 new dns configuration via the engine, the resolv.conf update only the first name server in the resov.conf and keeping the 2 others, but this is not good and not absolute, this will keep the host as out-of-sync for ever.
Engine will complain that the host has 3 name servers, but DC only one.
If user choose to set 1 name server, then all other name servers in the conf must be overridden.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171121184703.git173fe83.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Add host with 3 name servers, the management network should be with static bootproto, because all dhcp scenarios + DNS feature will end up as out-of-sync almost 100% of the time - See BZ 1451261
2. Go to the management network in the ui and set new 1 name servers in the DNS configuration checkbox in the edit network dialog.
3. Approve operation

Actual results:
resolv.conf was updated with the new name server, the first name server in the conf was overridden, but the 2 other name servers remain, which caused the engine to report that management network is out-of-sync, but he also report that the change was successfully applied(because managed to apply the change, but not absolutely).

Expected results:
User defined dns severs should be absolute, which means to override all name servers in the resolv.conf except the specified by the user and make the host in sync.

Comment 1 Michael Burman 2017-11-23 13:55:31 UTC
Created attachment 1358238 [details]
screenshot

Comment 2 Dan Kenigsberg 2018-08-01 11:55:33 UTC
Let us solve it when we move from ifcfg to nmstate