Deployment fails on overcloud nodes because chronyd takes more than 20 seconds to sync with source
Bug #1867362 reported by
David Vallee Delisle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
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-
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
This commit [1] was merged on the master branch. I open this bug to backport this patch to train.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
status: | Triaged → Fix Released |
milestone: | none → ussuri-3 |
To post a comment you must log in.
Fix proposed to branch: stable/train /review. opendev. org/712981
Review: https:/