Some log files are not rotated correctly in MOS 9.2

[TatyanaGladysheva]

Detailed bug description:
Some log files from /etc/logrotate.d folder are not rotated correctly on controllers. Example:

root@node-1:~# logrotate -f /etc/logrotate.d/pacemaker
error: skipping "/var/log/pacemaker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

root@node-1:~# logrotate -f /etc/logrotate.d/conntrackd
error: skipping "/var/log/conntrackd-stats.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/conntrackd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

root@node-1:~# logrotate -f /etc/logrotate.d/dpkg
error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
...

Steps to reproduce:
1. observe log files from 'ls -la /etc/logrotate.d' output
2. ssh to controller and run "logrotate -f /etc/logrotate.d/[0]", where [0] - log file from step 1 if it exists on controller

Expected results:
no errors, logs are rotated correctly

Actual result:
root@node-1:~# logrotate -f /etc/logrotate.d/pacemaker
error: skipping "/var/log/pacemaker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

Reproducibility:
100%

Environment:
MOS 9.2 snapshot #749

Additional information:
haproxy and puppet logs are rotated correctly after the bugs were fixed:
https://bugs.launchpad.net/fuel/+bug/1655029
https://bugs.launchpad.net/fuel/+bug/1581098

[Stanislaw Bogatkin (sbogatkin)]

Logrotate uses main conf file located at /etc/logrotate.conf
This file includes all the file from /etc/logrotate.d/
Also this file contains 'su root syslog' statement which eliminates the problem from this bug. As long as we apply logrotate by executing it with main config file, this bug has no sense. Closed as invalid.