Bug 1127806

Summary: apply ntp-server from the installer to the configuration
Product: Red Hat OpenStack Reporter: Mike Burns <mburns>
Component: rhel-osp-installerAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 7)CC: aberezin, rhos-maint, sasha, yeylon
Target Milestone: z1   
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: rhel-osp-installer-0.3.4-2.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-01 13:26:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Burns 2014-08-07 15:21:28 UTC
Description of problem:
The default kickstart reads ntp-server from the environment.  This should be applied from the installer.  We already ask for the ntp server so it's just a configuration step.

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

How reproducible:

Comment 7 Alexander Chuzhoy 2014-09-15 17:45:48 UTC
Failed-qa: rhel-osp-installer-0.3.4-3.el6ost.noarch

I see no reference to clock.redhat.com (nor the resolved IP) in ntp.conf on any of the deployed servers.

Comment 8 Marek Hulan 2014-09-16 09:19:14 UTC
Assigning back to QA, the subject of this BZ was not about configuring ntp.conf but to use configured NTP server during provisioning. It's part of %post task in KS template. You can verify it by looking at generated KS template, search for /usr/sbin/ntpdate.

Comment 9 Alexander Chuzhoy 2014-09-16 14:39:40 UTC
Verified: rhel-osp-installer-0.3.4-3.el6ost.noarch

As per comment #8, checked the anaconda file on the deployed machine - there's a line:

/usr/sbin/ntpdate -sub clock.redhat.com

Comment 11 errata-xmlrpc 2014-10-01 13:26:12 UTC
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.