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

Bug 2029916

Summary:	Excluding system facts logs as WARN causing log files to increase dramatically
Product:	[Community] Candlepin (Migrated to Jira)	Reporter:	Rehana <redakkan>
Component:	candlepin	Assignee:	candlepin-bugs
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.1	CC:	bcourt, dsynk, nmoumoul, redakkan, tasander
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	candlepin-4.1.9-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2029548	Environment:
Last Closed:	2022-01-20 10:16:49 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:
Bug Depends On:	2029548
Bug Blocks:

Description Rehana 2021-12-07 14:47:07 UTC

+++ This bug was initially created as a clone of Bug #2029548 +++

Description of problem:
When adding the option 'candlepin.consumer.facts.match_regex' /etc/candlepin/candlepin.conf we see all facts that are being excluded logged as WARN. Since this option is not included in the candlepin.conf file by default and it is manually being placed here, I do not believe the exclusions should be or a WARN type. Since this option is also used to exclude systems facts on hosts where the number of these facts are causing long queries or a lot of system resource usage, I believe these should be logged as DEBUG level in the logs to limit the unnecessary logging of INFO+.

Version-Release number of selected component (if applicable):
candlepin-3.1.28-1.el7sat.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Add regex exclusion to the candlepin.conf file for host facts and watch the logs for the matches to appear as WARN level.
2.
3.

Actual results:
Candlepin log files increase in size 3-4x 

Expected results:
This logging should be set on the level of DEBUG as this is an optional parameter to add for systems with a lot of facts.

Additional info: