Activity log for bug #1932128

Date Who What changed Old value New value Message
2021-06-16 08:46:28 Takashi Kajinami bug added bug
2021-06-16 08:46:58 Takashi Kajinami description Description =========== This was initially reported in https://bugzilla.redhat.com/show_bug.cgi?id=1972556 Currently, libvirt-daemon-driver-qemu is not installed in overcloud image. Because of that /etc/logrotate.d/libvirtd is not created in overcloud nodes and logs under /var/log/libvirt/qemu are never rotated. This means that the file can grow for example when many stop/start operation is executed. In addition, the file is never purged even after the instance is deleted. Because nova assigns a different id for each instances this would result in huge number of log files left. Steps to reproduce ================== * Deploy overcloud * Create and delete some instances * Check files under /var/log/libvirt/qemu/*.log in compute nodes after several days Expected result =============== Files are rotated and delete automatically Actual result ============= These files are never rotated Environment =========== Logs & Configs ============== N/A Description =========== This was initially reported in https://bugzilla.redhat.com/show_bug.cgi?id=1972556 Currently, libvirt-daemon-driver-qemu is not installed in overcloud image. Because of that /etc/logrotate.d/libvirtd is not created in overcloud nodes and logs under /var/log/libvirt/qemu are never rotated. This means that the file can grow for example when many stop/start operation is executed. In addition, the file is never purged even after the instance is deleted. Because nova assigns a different id for each instances this would result in huge number of log files left. Steps to reproduce ================== * Deploy overcloud * Create and delete some instances * Check files under /var/log/libvirt/qemu/*.log in compute nodes after several days Expected result =============== Files are rotated and delete automatically Actual result ============= These files are never rotated Environment =========== The problem was initially found in stable/train deployment but the same situation is observed in master. Logs & Configs ============== N/A