Red Hat Bugzilla – Bug 986830
Support to configure logrotate maxsize for Automated Installation
Last modified: 2014-01-21 14:46:01 EST
Description of problem: Currently rhev-h can support configure logrotate maxsize form TUI, but it doesn't support for Automated installation. So it would be better if RHEV-H support to configure logrotate maxsize for Automated Installation Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130222.0.auto1744.el6 ovirt-node-3.0.0-999.0.20130719134242gitb6ab8be.el6.noarch How reproducible: 100% Steps to Reproduce: Actual results: RHEV-H only support to configure logrotate maxsize for TUI. Expected results: It would be better if RHEV-H support to configure logrotate maxsize for Automated Installation. Additional info:
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 Test step: auto install with "BOOTIF=eth0 storage_init=/dev/sda logrotate_max_size=2048 firstboot" After auto install success, check that the item of "Logrotate Max Log Size" still shown "1024", and the size of the file "/etc/logrotate.d/ovirt-node " also didn't change. [root@dhcp-9-178 admin]# cat /etc/logrotate.d/ovirt-node /var/log/ovirt*.log { rotate 3 compress missingok size 1M create } So this bug hasn't fixed, need to re-assigned again.
Test version: rhevh-6.5-20131031.1.0.iso ovirt-node-3.0.1-7.el6 Test step: auto install with "BOOTIF=eth0 storage_init=/dev/sda logrotate_max_size=2048 firstboot" After auto install success, check that the item of "Logrotate Max Log Size" was shown "2048", and the size of the file "/etc/logrotate.d/ovirt-node " also changed. [root@dhcp-9-178 admin]# cat /etc/logrotate.d/ovirt-node /var/log/ovirt*.log { rotate 3 compress missingok size 2048 create } so this bug has been fixed, after the status of this bug change into "ON_QA", i will verify it.
According to comment 6, change the status of this bug into "VERIFIED"
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html