bad chronyd configuration prevents chronyd from starting during deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
High
|
Unassigned |
Bug Description
Looks like a problem with the chrony.conf.j2 template. /etc/chrony.conf does not start when configured during deployment
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
Nov 19 20:43:23 overcloud-
The generated config is:
# Do not manually edit this file.
# Managed by ansible-role-chrony
server 0.rhel.pool.ntp.org iburst
server 1.rhel.pool.ntp.org iburst
server 2.rhel.pool.ntp.org iburst
server 3.rhel.pool.ntp.org iburst
pool u'pool.ntp.org' iburst minpoll 6 maxpoll 10
bindcmdaddress 127.0.0.1
bindcmdaddress ::1
u'deny all' # <<--- line 10
driftfile /var/lib/
logdir /var/log/chrony
rtcsync
makestep 1.0 3
The "u'deny all' seems to be the culprit (the pool line is suspect as well). Changing this line to "deny all" allows the service to proceed.
Changed in tripleo: | |
status: | New → Confirmed |
milestone: | none → stein-2 |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Fixed by https:/ /review. openstack. org/#/c/ 614876/ . I think it's failing because we need a promotion.