Description of problem: Karaf logs for ODL are being rotated every 16M. Earlier they were being rotated every 10G and looking puppet-opendaylight, it looks like the default is still 10G. Not sure if tripleo is missing it up to cause
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install ODL + OSP13 with defaults configuration
Log files are being rotated every 17M leading to 10s of karaf log files
Log files were previously being rotated every 10G
log4j2.appender.rolling.policies.size.size = 16MB
Looks like puppet-opendaylight tries to configure 10G by default?
> External Bug ID: OpenDaylight Bug ODLPARENT-154
This issue does NOT have to await ODLPARENT-154 - it's (presumably) easy to do this locally in puppet-opendaylight - but it's really an indication that the default upstream could be better.
Was wondering about the status of this downstream? Also looks like we are capping the rotated logs at 7 files. This lead to me losing a ot of valuable logs when running longevity tests over the weekend. Can we increase the max rollovers atleast if we cant increase the log file size?
Puppet configures rollover at 2 with each file size of 10GB. Puppet also has a logic that
"logs to console + file"
configure file with above said size and rollover
and TripleO takes puppet to log to console. So the whole "else" section is not executed.
So who is setting the rollover to 7 in this case?
I will edit the above explained if-else logic in puppet-odl to also configure file size and rollover even if log_mechanism mentioned in TripleO is "console".
Since we are moving to logging to file in ODL, the logs files will be accordingly configured. This work is tracked at
No more changes needed for this bug. Hence closing it.