Deployment failing on NTP time sync task
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Committed
|
Undecided
|
Veronika Fisarova |
Bug Description
Description
===========
Release: wallaby
TripleO undercloud deployment is failing on the Task: Ensure system is NTP time synced, please refer to logs [1] and [2]. The most probable reason of failing is because the installed chronyd server is unable to connect with the NTP servers, by the deployment defaults to the pool.ntp.org servers.
Possible reasons why the connection cannot be established are:
1. None of the NTP pool servers is available
2. Missing or incorrect set firewall rules
3. Communication exceeded the 3sec on every pool
[1] https:/
[2] https:/
Related bugs:
https:/
If the time sync fails, then the whole deployment fails. A validation should be added to check if the chronyd can connect to the NTP pool and if it is retrieving time data (and not zeros). Nonetheless if the connection is still unsuccessful, user should be informed that they can add non-public NTP server as an extra var before the start of the deployment, e.g clock.corp.
description: | updated |
Changed in tripleo: | |
status: | New → Triaged |
description: | updated |
The patch was merged, see it at - https:/ /review. opendev. org/c/openstack /tripleo- validations/ +/858510