650919f527
Fixes an issue where multiple NTP daemons could be running on the
overcloud hosts, due to Kolla Ansible deploying a chrony container by
default starting with the Rocky release.
Kayobe now overrides this default, to ensure that chrony does not conflict
with the NTP daemon deployed on the host. To use the containerised chrony
daemon instead, set ``kolla_enable_chrony`` to ``true`` in
``${KAYOBE_CONFIG_PATH}/kolla.yml``. This will also disable the host NTP
daemon.
To ensure that chrony is not running, Kayobe removes the chrony container
if ``kolla_enable_chrony`` is ``false`` in the following commands:
* ``kayobe overcloud service deploy``
* ``kayobe overcloud service reconfigure``
* ``kayobe overcloud service upgrade``
The play in Kayobe is tagged with ``stop-chrony``.
Change-Id: I89a973c0b600abece79bddcba5a46cc28a4f1df9
Story: 2005272
Task: 30122
18 lines
602 B
YAML
18 lines
602 B
YAML
---
|
|
# NOTE(mgoddard): In the Rocky release, Kolla Ansible enabled the chrony
|
|
# container by default. Running this alongside the NTP daemon on the host is
|
|
# likely to cause issues, so we should explicitly disable it. Kolla Ansible
|
|
# won't automatically stop the container, so we do it here if it is disabled.
|
|
# See https://storyboard.openstack.org/#!/story/2005272.
|
|
|
|
- name: Stop the chrony container
|
|
hosts: overcloud
|
|
tags:
|
|
- stop-chrony
|
|
tasks:
|
|
- name: Stop the chrony container
|
|
docker_container:
|
|
name: chrony
|
|
state: absent
|
|
when: not kolla_enable_chrony | bool
|