Remote logfiles on Fuel master are not rotated

[Richard Berwald]

All messages that are send rsyslog in the container are logged inside the container in the directory /var/log/remote.
The directory /var/log of the container is mapped to /var/log/docker-logs of the Fuel master.
This results in all messages logged in the directory structure below /var/log/docker-logs/remote.

Logrotate on the Fuel master is configured to rotate to following files and directories (excerpt from /etc/logrotate.d/fuel.nodaily):
"/var/log/docker-logs/astute/*.log"
"/var/log/docker-logs/cobbler/*.log"
"/var/log/docker-logs/dnsmasq.log"
"/var/log/docker-logs/httpd/*.log"
"/var/log/docker-logs/mcollective.log"
"/var/log/docker-logs/messages"
"/var/log/docker-logs/nailgun/*.log"
"/var/log/docker-logs/nginx/*.log"
"/var/log/docker-logs/ostf*.log"
"/var/log/docker-logs/ostf/*.log"
"/var/log/docker-logs/rabbitmq/*.log"
"/var/log/docker-logs/rsync.log"
"/var/log/docker-logs/shotgun.log"
"/var/log/remote/[1-9]*/*.log"
"/var/log/remote/[1-9]*/*/*.log"

The directory /var/log/docker-logs/remote isn't mentioned anywhere, while the /var/log/remote directory exists, but is completely empty.

Not rotating the logfiles will in the end result in a full disk on the Fuel master, loss of information and possible non-functional Fuel master.

Fuel version information:
root@fuel-70 remote]# fuel fuel-version
DEPRECATION WARNING: /etc/fuel/client/config.yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_CUSTOM_SETTINGS environment variable.
api: '1.0'
astute_sha: 6c5b73f93e24cc781c809db9159927655ced5012
auth_required: true
build_id: '301'
build_number: '301'
feature_groups:
- experimental
- mirantis
fuel-agent_sha: 50e90af6e3d560e9085ff71d2950cfbcca91af67
fuel-library_sha: 5d50055aeca1dd0dc53b43825dc4c8f7780be9dd
fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
fuel-ostf_sha: 2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c
fuelmain_sha: a65d453215edb0284a2e4761be7a156bb5627677
nailgun_sha: 4162b0c15adb425b37608c787944d1983f543aa8
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: 486bde57cda1badb68f915f66c61b544108606f3
release: '7.0'
release_versions:
  2015.1.0-7.0:
    VERSION:
      api: '1.0'
      astute_sha: 6c5b73f93e24cc781c809db9159927655ced5012
      build_id: '301'
      build_number: '301'
      feature_groups:
      - experimental
      - mirantis
      fuel-agent_sha: 50e90af6e3d560e9085ff71d2950cfbcca91af67
      fuel-library_sha: 5d50055aeca1dd0dc53b43825dc4c8f7780be9dd
      fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
      fuel-ostf_sha: 2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c
      fuelmain_sha: a65d453215edb0284a2e4761be7a156bb5627677
      nailgun_sha: 4162b0c15adb425b37608c787944d1983f543aa8
      openstack_version: 2015.1.0-7.0
      production: docker
      python-fuelclient_sha: 486bde57cda1badb68f915f66c61b544108606f3
      release: '7.0'

[Maciej Relewicz (rlu)]

on

[root@fuel ~]# fuel fuel-version
api: '1'
auth_required: true
feature_groups: []
openstack_version: 2015.1.0-8.0
release: '8.0'

[root@fuel ~]# ls -lah /var/log/remote*
lrwxrwxrwx 1 root root 27 Dec 29 15:22 /var/log/remote -> /var/log/docker-logs/remote

so problem exist only on 7.0

[Denis Meltsaykin (dmeltsaykin)]

Richard, I cannot confirm your statement. It looks fine on my 7.0:

[root@nailgun ~]# ll /var/log/remote
lrwxrwxrwx 1 root root 27 May 11 12:30 /var/log/remote -> /var/log/docker-logs/remote

Please add more details about the issue you are experiencing.

[Richard Berwald (rberwald)]

Looking at the report date, this was reported against MU1. For Fuel 7 MU3, the bug seems to be fixed.
The issue was that /var/log/remote was an empty directory, not a link, at moment of reporting, while logrotate was pointing to /var/log/remote (and still is).

[Dmitry Pyzhov (dpyzhov)]

Bug is incomplete status for a month. Changing status to invalid. Please reopen the issue if you have more data.