Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1972556

Summary:	/var/log/libvirt/qemu/*.log is never rotated
Product:	Red Hat OpenStack	Reporter:	Takashi Kajinami <tkajinam>
Component:	openstack-tripleo-heat-templates	Assignee:	Bogdan Dobrelya <bdobreli>
Status:	CLOSED DUPLICATE	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	aschultz, bdobreli, dvd, mburns, mschuppe
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-29 17:07:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:	Train
Embargoed:

Description Takashi Kajinami 2021-06-16 07:47:44 UTC

Description of problem:

In RHOSP16.1, 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.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Deploy overcloud
2. Create and delete some instances
3. Check /var/log/libvirt/qemu/ after several days

Actual results:
The log files are not rotated and left


Expected results:
The log files are rotated and delete dafter a while

Additional info:

Comment 1 Bogdan Dobrelya 2021-09-21 12:15:23 UTC

There is also https://bugzilla.redhat.com/show_bug.cgi?id=2005340 that can be fixed with the same linked patch

Comment 2 Bogdan Dobrelya 2021-11-29 17:07:42 UTC


*** This bug has been marked as a duplicate of bug 2022736 ***