Unconsistent logrotate configuration on master node in mitaka release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Alexey Stupnikov | ||
Newton |
In Progress
|
Medium
|
Fuel Sustaining |
Bug Description
There is an intersection between general logrotate configuration and fuel.nodaily runs in MOS9 (but not MOS10). This is not a critical problem itself, but some application could need a special treatment when their logs are rotated. We have to analyse possible impact and modify logrotate configuration if some problems are possible.
There are two logrotate statements for the following log files:
[root@localhost logrotate.d]# grep -r /var/log/cobb /etc/logrotate.d
/etc/logrotate.
/etc/logrotate.
/etc/logrotate.
/etc/logrotate.
[root@localhost logrotate.d]# grep -r /var/log/http /etc/logrotate.d
/etc/logrotate.
/etc/logrotate.
[root@localhost logrotate.d]# grep -r /var/log/nail /etc/logrotate.d
/etc/logrotate.
/etc/logrotate.
/etc/logrotate.
[root@localhost logrotate.d]# grep -r /var/log/rabbi /etc/logrotate.d
/etc/logrotate.
/etc/logrotate.
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
milestone: | 9.x-updates → 9.2-mu-3 |
Changed in fuel: | |
status: | In Progress → Fix Committed |
Setting this bug's importance to medium as it is a 'Failure of a significant feature, with workaround'. WA is to delete duplicate logrotate configuration entries from /etc/logrotate. d/fuel. nodaily file.
We can re-open and fix this issue if this bug will become customer-found.