RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The setting of ntp server won't be effective after applying the
configuring. The ip of the ntp server ip is still the original one. Let
it there, press the the "Apply" again, the value we set last time will be
effective. 


Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120502.3.el6

How reproducible:
100%

Steps to Reproduce:
1. enter rhev-h TUI, select the "Network" item
2. configure the NTP Server ip and Apply it
3. check the ntp server ip in TUI or /etc/ntp.conf
  
Actual results:
The ip we set isn't effective after choosing "Apply" in TUI, the ntp
server is still the original value. Don't take other action, just
choosing the "Apply", the ip we set last time is effective. If you do
nothing, just select the "Apply" in TUI, the ntp server value will
alternates between the original value and the one we set.

Expected results:
The ntp server is effective after "Apply". If we don't change the ntp
server and select "Apply" directly, the ntp server ip shouldn't change.

Additional info:

Verified with the latest build rhev-hypervisor6-6.3-20120516.0.el6. Choose the network as static, the set ntp server will be effective.

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-2012-0741.html