logrotate.d does not have correct info
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Megh Bhatt | |||
R2.21.x |
Fix Committed
|
Medium
|
Megh Bhatt | |||
R3.0 |
Fix Committed
|
Medium
|
Megh Bhatt | |||
R3.1 |
Fix Committed
|
Medium
|
Megh Bhatt | |||
Trunk |
Fix Committed
|
Medium
|
Megh Bhatt |
Bug Description
Following logs have logrotate issue. (I think /var/log/
#### /etc/logrotate.
Typo
/var/log/
/var/log/
Need following logs?
contrail-
anything else?
#### /etc/logrotate.
Typo
/var/log/
Need following logs?
contrail-
contrail-
schema-zk.log
api-0-zk.log
contrail-
device-
svc-monitor-zk.log
contrail-
contrail-
anything else?
#### /etc/logrotate.
Need following logs?
contrail-
contrail-dns.log
contrail-
contrail-named.log
contrail-
anything else?
#### /etc/logrotate.
Not used
ifmap-server-
### TSN / Compute node do not have /etc/logroted.d
information type: | Proprietary → Public |
tags: | added: customer |
tags: | added: bms |
tags: | added: analytics |
By default, the daemons (c++ and python) are using internal loggers that do the rotation of the files themselves and hence we do not really need the log rotate entries. However, we do need log rotate for the -stdout/stderr.log files and as part of this bug, we will cleanup the log rotate to just include those files. We will need corresponding change in supervisor conf files to disable supervisord doing the rotation.