Bug 1438367

Summary: After controllers reboot time is not NTP synchronized anymore
Product: Red Hat OpenStack Reporter: Sadique Puthen <sputhenp>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: achernet, adhingra, agurenko, aschultz, athomas, augol, dbecker, emacchi, jjoyce, jschluet, mburns, mcornea, morazi, ohochman, rhel-osp-director-maint, slinaber, tvignaud
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-2.0.0-47.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1430833 Environment:
Last Closed: 2017-05-18 14:33:20 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:
Embargoed:
Bug Depends On: 1429221, 1429222, 1430833    
Bug Blocks:    

Comment 1 Sadique Puthen 2017-04-03 09:06:24 UTC 
MyRepubic hit this issue in their production on OSP9 which caused an outage as Ceph monitors misbehaved due to clock skew and stopped writing to storage.

Requesting for a backport to OSP9
Comment 3 Gurenko Alex 2017-04-20 09:05:35 UTC 
Verified on build:
[stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed
9   -p 2017-04-07.5

After reboot:

[heat-admin@controller-0 ~]$ timedatectl
      Local time: Thu 2017-04-20 09:04:41 UTC
  Universal time: Thu 2017-04-20 09:04:41 UTC
        RTC time: Thu 2017-04-20 09:04:40
       Time zone: UTC (UTC, +0000)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: n/a
Comment 7 errata-xmlrpc 2017-05-18 14:33:20 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.

https://access.redhat.com/errata/RHBA-2017:1251