kolla-ansible/bug-1915528-chronyd-crash-loop-if-server-is-rebooted-debian.yaml at 591f366ed736977664e899bd834e363191a9472d - kolla-ansible - OpenDev: Free Software Needs Free Tools

openstack/kolla-ansible

Ana Peric 21ccae12f7 chronyd crash loop if Debian server is rebooted

This patch fixes the constant chrony container crash loop after (Debian 10) server is rebooted,
as described in Bug-ID: #1915528.

Due to permissions issue, before this fix is applied chronyd process will be exiting with
root cause error message:

Fatal error : Could not open configuration file /etc/chrony/chrony.conf : Permission denied
This has to do with priviledges we configured for chrony. Relaxing them fixes the issue.
Tested on top of stable/victoria and Debian 10 Buster.

Not tested on CentOS/RHEL. If this does not work well on RHEL/CentOS we can maybe parametrise
the owner and make it configurable (just one idea).

Closes-Bug: #1915528
Change-Id: I71f45ba5b9d1d2227c95633d3de51e2ccd42a467

2021-02-17 20:09:45 +01:00

6 lines

127 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     chronyd crash loop if server is rebooted (Debian)
     `LP#1915528 <https://launchpad.net/bugs/1915528>`__