Bug 2280656

Description of problem:
Controller disks fill up with the default 10G /var/log partition before logs rotate out.

Version-Release number of selected component (if applicable):
17 and 17.1

How reproducible:
100%

Steps to Reproduce:
1. Deploy
2. Operate
3. Fail

Actual results:
Controllers lock up with full disks

Expected results:
Controllers function and rotate logs without filling the partition

Additional info:

Re-opening this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2165470. It has not been solved adequately in documentation.  I have a customer that has run into it again.  A 10G partition for /var/log is not sufficient for /var/log/messages.    The default logrotate is set to:

# rotate log files weekly
weekly

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# use date as a suffix of the rotated file
dateext

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

While the messages file grows far too large to last the 4 week rotation

[root@leaf1-controller-1 log]# du -a /var/log | sort -n -r | head -n 10
9936860 /var/log
2684312 /var/log/messages-20230212
2683540 /var/log/messages-20230205
2310812 /var/log/messages-20230129
940728  /var/log/messages
650404  /var/log/messages-20230122
354744  /var/log/containers
143412  /var/log/containers/httpd
67392   /var/log/sa
49436   /var/log/journal/357b886700b24d5bb84c8e12b910bf6e

The default size for /var/log should be far greater than 10G with the current logrotate config. I know we can override the logrotate config for /var/log/containers. What about the default system logrotate for /var/log ?