Bug 1629905

Summary:	xClarity: LXCA events cause large increases in log/db size due to event collection
Product:	Red Hat CloudForms Management Engine	Reporter:	Rodney H. Brown <rbrown4>
Component:	Providers	Assignee:	Bronagh Sorota <bsorota>
Status:	CLOSED ERRATA	QA Contact:	Rodney H. Brown <rbrown4>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.9.3	CC:	dgouveia, dmetzger, gblomqui, jfrey, jhardy, lavenel, obarenbo, simaishi, smallamp
Target Milestone:	GA
Target Release:	5.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.10.0.16	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1560074	Environment:
Last Closed:	2019-02-07 23:03:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Lenovo	Target Upstream Version:
Embargoed:
Bug Depends On:	1560074
Bug Blocks:	1560089

Description Rodney H. Brown 2018-09-17 15:48:03 UTC

Description of problem:
The EVM log becomes full very quickly when a large number of events is received from multiple LXCA instances. This may cause the VM to become unusable


How reproducible:
Manage multiple LXCAs and generate activity on each (i.e. power of machines, insert components etc.)

Steps to Reproduce:
1. Manage multiple LXCAs
2. Observe the VM over the course of a week
3. Observe the size the evm log file and DB size to view the increases.

Actual results:


Expected results:

Comment 2 Rodney H. Brown 2018-09-17 15:49:18 UTC

Related to Pull Request:  https://github.com/ManageIQ/manageiq-providers-lenovo/pull/223

Comment 4 Rodney H. Brown 2018-11-13 20:14:36 UTC

Verified in build 5.10.0.20.20181016163900_fe677b4

Comment 5 errata-xmlrpc 2019-02-07 23:03:43 UTC

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.

https://access.redhat.com/errata/RHSA-2019:0212