Hide Forgot
Description of problem: After configure dns & ntp server in network UI, cannot save these server info to configure file. (/etc/resolv.conf, /etc/ntp.conf) Version-Release number of selected component (if applicable): rhev-hypervisor-6.1-20110420 How reproducible: Always. Steps to Reproduce: 1. configure dns & ntp server in network UI. 2. check config file. (/etc/resolv.conf, /etc/ntp.conf) Actual results: no configure info in config files. Expect Results: dns & ntp server info are saving to configle file correctly.
*** Bug 710858 has been marked as a duplicate of this bug. ***
Tested on 6.2-0.12: 1. set static ip 2. set dns server. 3. after apply, no dns info list in "DNS Server" 4. check /etc/resolv.conf, it's blank.
On the autobuild 6.2-0.12.hybrid1313452873, fill dns server and apply, it jump to network interface configure page, drop to shell check /etc/resolv.conf, it's still blank. /etc/resolv.conf is not persisted also: #cat /config/files | grep resolv no results.
BTW, the "apply" button should not jump to network interface configure page, could you fix it in this bug or should I report a new bug for it?
I can reproduce 100% on 6.2-0.14, but very strange (see below): 1. configure static network. 2. give one dns entry and apply. /etc/resolv.conf is empty. 3. give two dns entry and apply. /etc/resolv.conf show both dns entries in line #2 #3, the first line is blank.
Based on Comment 19, move back to assigned
Have the same problem, but only when entering just the one nameserver. If I add the same nameserver twice the setting persists.
Verified on 6.2-0.15: 1. with static ip: a. set one dns server and one ntp server. dns and ntp server are saved to file correctly. b. set two dns server and two ntp server. dns and ntp server are saved to file correctly. 2. with dhcp, ntp is disabled by purpose. (see bug 717532): a. set one dns server. dns are saved to file correctly. b. set two dns server. dns are saved to file correctly. set bug status to verified.
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. http://rhn.redhat.com/errata/RHBA-2011-1783.html