heka read log permission denied

It seems that that "other" does not have read access to mariadb.log:

[root@control01 ~]# ls -lah /var/lib/docker/volumes/kolla_logs/_data/mariadb/
totalt 40K
drwxr-xr-x. 2 polkitd systemd-network 24 18 jan 12.39 .
drwxrwxr-x. 15 root buser 4,0K 18 jan 12.59 ..
-rw-rw----. 1 polkitd systemd-network 34K 19 jan 10.02 mariadb.log

nor dnsmasq.log:

[root@control01 ~]# ls -lah /var/lib/docker/volumes/kolla_logs/_data/neutron/
totalt 4,2M
drwxr-xr-x. 2 polkitd polkitd 4,0K 18 jan 13.15 .
drwxrwxr-x. 15 root buser 4,0K 18 jan 12.59 ..
-rw-r-----. 1 nobody root 8,1K 19 jan 02.00 dnsmasq.log
-rw-r--r--. 1 polkitd polkitd 35K 18 jan 14.08 neutron-dhcp-agent.log
-rw-r--r--. 1 polkitd polkitd 20K 18 jan 14.07 neutron-l3-agent.log
-rw-r--r--. 1 polkitd polkitd 4,5K 18 jan 14.00 neutron-metadata-agent.log
-rw-r--r--. 1 root root 379 18 jan 13.14 neutron-ns-metadata-proxy-a2d8c1cf-c353-4116-b0f4-ca03d93bdec2.log
-rw-r--r--. 1 root root 2,9K 18 jan 14.00 neutron-ns-metadata-proxy-abc006f5-c346-4958-bb26-02b37854d120.log
-rw-r--r--. 1 root root 379 18 jan 13.15 neutron-ns-metadata-proxy-d7508fce-8611-46a0-b473-61f8af101e13.log
-rw-r--r--. 1 polkitd polkitd 53K 18 jan 17.36 neutron-openvswitch-agent.log
-rw-r--r--. 1 polkitd polkitd 3,9M 19 jan 10.09 neutron-server.log

To add to previous comment, I am running Kolla 3.0.2.

In master，heka already removed.
If you want to fix the problem in ocata.
Please change follow code.
https://github.com/openstack/kolla/blob/stable/ocata/docker/heka/Dockerfile.j2#L8

dest

{{ macros.configure_user(name='heka', homedir='/var/cache/hekad') }}

to

{{ macros.configure_user(name='heka', homedir='/var/cache/hekad', groups='mysql,neutron') }}

rebuild heka image.

Sorry,There was a mistake in the last reply.
{{ macros.configure_user(name='heka', homedir='/var/cache/hekad', groups='mysql,root') }}

since heka is removed in master, should this be closed?

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA