Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:

This is the logrotate configuartion where maxsize is set to 100M for noobaa.log

[root@new-12 ~]# cat /etc/logrotate.d/noobaa-logrotate

/var/log/noobaa.log

{     daily     maxsize 100M      minsize 10M     start 1     missingok     rotate 100     compress     create 644 root root     sharedscripts     postrotate         killall -HUP rsyslogd || true         killall -HUP syslogd || true         systemctl reload syslog-ng > /dev/null 2>&1 || true     endscript }

 

/var/log/noobaa_events.log

{     daily     maxsize 100M     minsize 10M     start 1     missingok     rotate 100     compress     create 644 root root     sharedscripts     postrotate         killall -HUP rsyslogd || true         killall -HUP syslogd || true         systemctl reload syslog-ng > /dev/null 2>&1 || true     endscript }

 

/var/log/client_noobaa.log

{     size 100M     start 1     missingok     rotate 10     compress     create 644 root root     sharedscripts     postrotate         killall -HUP rsyslogd || true         killall -HUP syslogd || true         systemctl reload syslog-ng > /dev/null 2>&1 || true     endscript }

And these are the noobaa log files in which files size are exceeding the limit of 100M.

[root@lokiprt013 log]# ls -lh /var/log/ | grep noobaa

drwx------. 3 root    root      23 May 15 00:00 noobaa{}

rw-rr-. 1 root    root    127M Aug 25 17:55 noobaa_events.log

rw-rr-. 1 root    root    447K Aug 20 03:42 noobaa_events.log-20250820.gz

rw-rr-. 1 root    root    3.7M Aug 23 03:32 noobaa_events.log-20250823.gz

rw-rr-. 1 root    root    7.2M Aug 24 03:38 noobaa_events.log-20250824.gz

rw-rr-. 1 root    root    6.6M Aug 25 03:40 noobaa_events.log-20250825.gz

rw-rr-. 1 root    root    8.7G Aug 25 23:48 noobaa.log

rw-rr-. 1 root    root     41M Aug 12 03:37 noobaa.log-20250812.gz

rw-rr-. 1 root    root     54M Aug 13 03:24 noobaa.log-20250813.gz

rw-rr-. 1 root    root     58M Aug 14 03:24 noobaa.log-20250814.gz

rw-rr-. 1 root    root     28M Aug 15 03:18 noobaa.log-20250815.gz

rw-rr-. 1 root    root     28M Aug 16 03:12 noobaa.log-20250816.gz

rw-rr-. 1 root    root     29M Aug 17 03:29 noobaa.log-20250817.gz

rw-rr-. 1 root    root     28M Aug 18 03:06 noobaa.log-20250818.gz

rw-rr-. 1 root    root    213M Aug 19 03:33 noobaa.log-20250819.gz

rw-rr-. 1 root    root    417M Aug 20 03:40 noobaa.log-20250820.gz

rw-rr-. 1 root    root    424M Aug 21 03:38 noobaa.log-20250821.gz

rw-rr-. 1 root    root    484M Aug 22 03:47 noobaa.log-20250822.gz

rw-rr-. 1 root    root    483M Aug 23 03:30 noobaa.log-20250823.gz

rw-rr-. 1 root    root    226M Aug 24 03:37 noobaa.log-20250824.gz

rw-rr-. 1 root    root    566M Aug 25 03:37 noobaa.log-20250825.gz

 

The behaviour is that log rotation is happening on daily basis, but the size of the file is exceeding the max size limit.
 
Ex: rw-rr-. 1 root    root    8.7G Aug 25 23:48 noobaa.log
This file has reached to 8.7G size.

Even after rotation, the file size is still greater than 100M
Ex: 566M for noobaa.log-20250825.gz