| Summary: | openstack-packstack: ntp servers aren't configured after the server's reboot | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Yogev Rabl <yrabl> | ||||||||
| Component: | openstack-packstack | Assignee: | Martin Magr <mmagr> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Nir Magnezi <nmagnezi> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.0 | CC: | aberezin, ajeain, aortega, derekh, hateya, mlopes, mmagr, sclewis, yeylon | ||||||||
| Target Milestone: | beta | ||||||||||
| Target Release: | 4.0 | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 1034358 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2013-12-20 00:19:54 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: | |||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1034358 | ||||||||||
| Attachments: |
|
||||||||||
|
Comment 2
Yogev Rabl
2013-08-22 09:01:00 UTC
Created attachment 789101 [details]
The openstack-packstack answer file
Created attachment 789102 [details]
the ntp conf file
Created attachment 789152 [details]
The log files archived.
It should be fixed in the current release. Auto adding >= MODIFIED bugs to beta Verified NVR: openstack-packstack-2013.2.1-0.20.dev936.el6ost.noarch 1. Installed openstack via packstack , used a local NTP server (See comment #2). 2. Rebooted the server. Result: ======= NTP configuration remains the same post reboot. 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/RHEA-2013-1859.html |