Bug 741190
Summary: | VDSM: /etc/logrotate.d/libvirtd contains bad data, causes e-mail flood from cron | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Daniel Paikov <dpaikov> |
Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
Status: | CLOSED ERRATA | QA Contact: | Daniel Paikov <dpaikov> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | abaron, acathrow, bazulay, hateya, iheim, mzhan, rwu, veillard, whuang, ykaul |
Target Milestone: | rc | ||
Target Release: | 6.2 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.9-107 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 07:28:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Daniel Paikov
2011-09-26 08:04:02 UTC
/etc/logrotate.d/libvirtd is a file owned by libvirt package: [root@test ~]# rpm -qf /etc/logrotate.d/libvirtd libvirt-0.9.4-12.el6.x86_64 [root@test ~]# rpm -V libvirt .M....... /var/cache/libvirt/qemu [root@test ~]# cat /etc/logrotate.d/libvirtd /var/log/libvirt/libvirtd.log { weekly missingok rotate 4 compress delaycompress copytruncate minsize 100k } [root@test ~]# But as you can see its content contains only one entry and no comment about vdsm. My guess is that the extra definitions are added by vdsm in some ways, and the bug should be retargetted at this component, Daniel Did you find a reliable way to reproduce this condition? Does removing vdsm and installing it solves the problem? Didn't find a way to reproduce yet, but I have this issue on all my hosts. yum remove vdsm / yum install vdsm makes /etc/logrotate.d/libvirtd go back to normal. How do we test this? (In reply to comment #7) > How do we test this? try install/upgrade/uninstall ov vdsm and make sure that never ever do you get multiple "vdsm" stanzas in logrotate.d/libvirtd, and that no nagging email is sent due to vdsm installation. (In reply to comment #8) > (In reply to comment #7) > > How do we test this? > > try install/upgrade/uninstall ov vdsm and make sure that never ever do you get > multiple "vdsm" stanzas in logrotate.d/libvirtd, and that no nagging email is > sent due to vdsm installation. What about hosts that already have this problem? Does it fix it retroactively? (In reply to comment #9) > > What about hosts that already have this problem? Does it fix it retroactively? it should. Upgraded to 4.9-107, the file still has multiple instances of the same garbage. Moving back to ASSIGNED. upgraded from what? did the garbage exist beforehence? would the secret service vdsmd reconfigure remove it? Either way, it is a bit too late to handle these minor details. If vdsm does not add multiple stanzas, that's good enough for 3.0. I wish I could take back my comment 10. Upgraded from 106 to 107. service vdsmd reconfigure does help. The file now looks like this and logrotate doesn't have any output. [root@orange-vdsf ~]# cat /etc/logrotate.d/libvirtd # vdsm /var/log/libvirtd.log { rotate 100 missingok copytruncate size 15M compress compresscmd /usr/bin/xz uncompresscmd /usr/bin/unxz compressext .xz } # end vdsm /var/log/libvirt/libvirtd.log { weekly missingok rotate 4 compress delaycompress copytruncate minsize 100k } Checked on 4.9-108. 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/RHEA-2011-1782.html |