Bug 1483889 - Custom Id is not persisted to the database
Summary: Custom Id is not persisted to the database
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.1.6
Assignee: Eli Mesika
QA Contact: Pavel Stehlik
Depends On:
TreeView+ depends on / blocked
Reported: 2017-08-22 08:36 UTC by Eli Mesika
Modified: 2019-04-28 14:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-09-19 10:02:18 UTC
oVirt Team: Infra
rule-engine: ovirt-4.1+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 80907 0 master MERGED core: Custom Id is not persisted to the database 2017-08-28 10:25:32 UTC
oVirt gerrit 81141 0 ovirt-engine-4.1 MERGED core: Custom Id is not persisted to the database 2017-08-29 10:01:00 UTC

Description Eli Mesika 2017-08-22 08:36:57 UTC
Description of problem:

When creating a audit log record, there is an option to assign a custom id string to the record, this is use for example when dealing with interfaces where the custom id value gets the interface name in order to handle event flooding correctly.
However, the custom is value is used when generating the key for the audit log cache but since it is not persisted to the database, each record in the cache that has a non-empty custom id value will not be cleaned from the cache since the key for searching this record will have always an empty custom id value.

This behavior may lead to cache flooding and memory leak.

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

How reproducible:

Internal to code, can be tested only in developer environment using the debugger.

Steps to Reproduce:

Actual results:

custom id is not persisted to he database causing some events not to be cleared from cache

Expected results:

custom id should be persisted to the database in order that the key stored in the cache and the key generated to search the cache will have the same value.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.