Description of problem:
As far as I checked tripleo_ansible/playbooks/cli-overcloud-node-growvols.yaml[1], it seems that the default size of /var/log partition is 10GB for a overcloud node.
On the other hand, podman health-check outputs too many lines into /var/log/messages.
So, this will probably may cause disk full in a short time in most customer's environment which uses default setting.
Actually, one of our customers already faced the problem in their testing environment.
I guess that we should increase the default size of /var/log partition or write a note that customers should increase /var/log/partition in our documentation such as [2].
[1] tripleo_ansible/playbooks/cli-overcloud-node-growvols.yaml:
~~~
- name: Overcloud Node Grow Volumes
hosts: allovercloud
any_errors_fatal: true
gather_facts: false
vars:
role_growvols_args:
default:
/=8GB
/tmp=1GB
/var/log=10GB
/var/log/audit=2GB
/home=1GB
/var=100%
Controller:
/=8GB
/tmp=1GB
/var/log=10GB
/var/log/audit=2GB
/home=1GB
/var=90%
/srv=10%
ObjectStorage:
/=8GB
/tmp=1GB
/var/log=10GB
/var/log/audit=2GB
/home=1GB
/var=10%
/srv=90%
~~~
[2]
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html-single/director_installation_and_usage/index#proc_configuring-whole-disk-partitions-for-object-storage_ironic_provisioning
Version-Release number of selected component (if applicable):
tripleo-ansible-3.3.1-0.20221208161843.fa5422f.el9os
How reproducible:
always
Steps to Reproduce:
1. overcloud install
2.
3.
Actual results:
The size of /var/log partition is 10GB
Expected results:
The size of /var/log partition should be increased more.
Additional info:
The team needs to discuss this further.
We provide what we believe is a reasonable default, and it can be edited by a customer.
It does appear thought, that there are cases where the logging output can be far more than we normally expect.
The team will discuss in it's next bug triage session.
Description of problem: As far as I checked tripleo_ansible/playbooks/cli-overcloud-node-growvols.yaml[1], it seems that the default size of /var/log partition is 10GB for a overcloud node. On the other hand, podman health-check outputs too many lines into /var/log/messages. So, this will probably may cause disk full in a short time in most customer's environment which uses default setting. Actually, one of our customers already faced the problem in their testing environment. I guess that we should increase the default size of /var/log partition or write a note that customers should increase /var/log/partition in our documentation such as [2]. [1] tripleo_ansible/playbooks/cli-overcloud-node-growvols.yaml: ~~~ - name: Overcloud Node Grow Volumes hosts: allovercloud any_errors_fatal: true gather_facts: false vars: role_growvols_args: default: /=8GB /tmp=1GB /var/log=10GB /var/log/audit=2GB /home=1GB /var=100% Controller: /=8GB /tmp=1GB /var/log=10GB /var/log/audit=2GB /home=1GB /var=90% /srv=10% ObjectStorage: /=8GB /tmp=1GB /var/log=10GB /var/log/audit=2GB /home=1GB /var=10% /srv=90% ~~~ [2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html-single/director_installation_and_usage/index#proc_configuring-whole-disk-partitions-for-object-storage_ironic_provisioning Version-Release number of selected component (if applicable): tripleo-ansible-3.3.1-0.20221208161843.fa5422f.el9os How reproducible: always Steps to Reproduce: 1. overcloud install 2. 3. Actual results: The size of /var/log partition is 10GB Expected results: The size of /var/log partition should be increased more. Additional info: