To Reproduce Steps to reproduce the behavior:

1. Deploy RHOSO18 control plane and dataplane

Expected behavior

• maxsize in logroate configuration should not be set by default.

Bug impact

• By default maxsize in logrotate.conf sets 10M. However, there is a request from a customer that they just want to manage the log rotation by time-based not size-based.
  Currently, the customer needs to set the large enough value to edpm_logrotate_crond_maxsize to set maxsize in logrotate.conf

Known workaround

• Set the large enough value to edpm_logrotate_crond_maxsize.

Additional context

• In RHOSO18, by default, we use journal for openstack service logs. However, there is a customer who wants to manages the logs in the previous way provided in OSP17.1 or earlier.

In such case, logs are rotated by logrotate-crond container but the default configuration are below.

# cat /var/lib/config-data/ansible-generated/crond/etc/logrotate-crond.conf 
/var/log/containers/*/*log /var/log/containers/*/*/*log /var/log/containers/*/*err {
  daily
  rotate 14
  maxage 14
  # minsize 1 is required for GDPR compliance, all files in
  # /var/log/containers not managed with logrotate will be purged!
  minsize 1
  # Do not use size as it's not compatible with time-based rotation rules
  # required for GDPR compliance.
  maxsize 10M
  missingok
  notifempty
  copytruncate
  delaycompress
  compress
}