Bug 1255101

Summary: Network TUI display two NTP servers when you configure only one NTP server on TUI
Product: Red Hat Enterprise Virtualization Manager Reporter: Chaofeng Wu <cwu>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.4CC: cshao, ecohen, gklein, huiwa, huzhao, lsurette, yaniwang, ycui
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-30 13:23:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chaofeng Wu 2015-08-19 15:39:13 UTC 
Description of problem:
Configure only one NTP server on TUI, then reboot the system, the TUI will show two NTP server.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.1-20150813.0.iso

How reproducible:
100%

Steps to Reproduce:
1. Install rhev-hypervisor7-7.1-20150813.0.iso, configure the network with dhcp mode, reboot the system.
2. Configure the NTP server with "clock.redhat.com", leave the other NTP server line with blank, then save.
3. Then reboot the system, check the NTP server on network TUI.

Actual results:
After step3, there are two NTP server on network TUI.

Expected results:
After step3, there should be only one NTP server on network TUI.

Additional info:
Drop into shell you can find that:
[root@localhost admin]# cat /etc/ntp.conf 
driftfile /var/lib/ntp/drift
includefile /etc/ntp/crypto/pw
keys /etc/ntp/keys
server clock.redhat.com
server 10.5.26.10   # added by /sbin/dhclient-script
server 10.5.27.10   # added by /sbin/dhclient-script

BTW, if you configure the network with static mode, this issue is gone.
Comment 1 Fabian Deutsch 2015-09-30 13:23:12 UTC 
The issues seems to be that dhcp is adding additional NTP servers, so the system is behaving as expected.

Independently of that this functionality will move to a different component, thus I'm closing this bug on this component.