21ccae12f7
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
24 lines
575 B
Django/Jinja
24 lines
575 B
Django/Jinja
{
|
|
"command": "/usr/sbin/chronyd -d -f /etc/chrony/chrony.conf",
|
|
"config_files": [
|
|
{
|
|
"source": "{{ container_config_directory }}/chrony.conf",
|
|
"dest": "/etc/chrony/chrony.conf",
|
|
"owner": "root",
|
|
"perm": "0644"
|
|
}
|
|
],
|
|
"permissions": [
|
|
{
|
|
"path": "/var/log/kolla/chrony",
|
|
"owner": "chrony:kolla",
|
|
"recurse": true
|
|
},
|
|
{
|
|
"path": "/var/lib/chrony",
|
|
"owner": "chrony:chrony",
|
|
"recurse": true
|
|
}
|
|
]
|
|
}
|