Bug 1813363 - Deployment fails on overcloud nodes because chronyd takes more than 20 seconds to sync with source
Summary: Deployment fails on overcloud nodes because chronyd takes more than 20 second...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 16.0 (Train on RHEL 8.1)
Assignee: David Vallee Delisle
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-13 15:28 UTC by David Vallee Delisle
Modified: 2023-12-15 17:34 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.3.2-0.20200314105722.ee3e63e.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-14 12:16:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1867362 0 None None None 2020-03-13 15:40:35 UTC
OpenStack gerrit 688672 0 None MERGED Replace chronyc "waitsync" with "makestep" 2020-05-20 18:54:49 UTC
OpenStack gerrit 712981 0 None MERGED Replace chronyc "waitsync" with "makestep" 2020-05-20 18:54:49 UTC
Red Hat Issue Tracker OSP-30810 0 None None None 2023-12-15 17:34:09 UTC
Red Hat Product Errata RHBA-2020:2114 0 None None None 2020-05-14 12:16:36 UTC

Description David Vallee Delisle 2020-03-13 15:28:40 UTC 
Description of problem:
When HW clock is out of sync, chrony can take a while to sync up (I've seen something like 7 minutes before it was in-sync).

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-11.3.2-0.20200211065544.d3d6dc3.el8ost.noarch

How reproducible:
All the time

Steps to Reproduce:
1. set hw clock on an overcloud node to be like 1h late
2. deploy

Actual results:
"chronyc waitsync 20" fails


Expected results:
Should complete
Comment 1 David Vallee Delisle 2020-03-13 15:29:27 UTC 
I'll be backporting the patch downstream.
Comment 2 Alex Schultz 2020-03-13 18:44:45 UTC 
Lowering the severity as this seems to be an environmental thing due to ntp servers being used. We always recommend using multiple sources as it'll prevent this from occurring.

Mar 11 12:58:10 txslst11nce-novacompute-0 cloud-init[4582]: + chronyc waitsync 20
Mar 11 13:01:32 txslst11nce-novacompute-0 chronyd[2657]: Source 2607:f160:a:1:c0:fe0:0:a000 offline                                                                        
Mar 11 13:05:39 txslst11nce-novacompute-0 ansible-stat[16301]: Invoked with path=/etc/chrony.conf follow=False get_checksum=True checksum_algorithm=sha1 get_mime=True get_attributes=True get_md5=None
Comment 20 errata-xmlrpc 2020-05-14 12:16:18 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-2020:2114
Note You need to log in before you can comment on or make changes to this bug.