Bug 804127 – [RFE] no logging property for Katello

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 804127 - [RFE] no logging property for Katello

Summary:	[RFE] no logging property for Katello

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Content Management (Show other bugs)
Sub Component:
Version:	6.0.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Justin Sherrill
QA Contact:	Og Maciel
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, Triaged

Depends On:
Blocks:	785722
	Show dependency tree / graph

Reported:	2012-03-16 11:27 EDT by Garik Khachikyan
Modified:	2015-01-04 16:59 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	System Engine had no configurable log levels due to the lack of access to the configuration object for environment initializers. This fix creates a new logging option in the configuration file (katello.yml) to allow different log levels.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-12-04 14:43:03 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2012:1543	normal	SHIPPED_LIVE	Important: CloudForms System Engine 1.1 update	2012-12-04 19:39:57 EST

Groups: None (edit)

Description Garik Khachikyan 2012-03-16 11:27:14 EDT

Description of problem:
Seems there is no logging level property to set (default seems warning).
Communication with developers says:
"KATELLO_LOGGING=${KATELLO_LOGGING:-warn}" system env. to use. Really there is no (more usual) way of using logging setting in property file?

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

How reproducible:
on default settings of Katello install there is no property in configs for logging level changes

Steps to Reproduce:
1.try to follow katello logs.
2.
3.
  
Actual results:
error level logs only

Expected results:
way to configure to have lower level logging in property file(s)

Additional info:

Comment 1 Justin Sherrill 2012-03-23 15:45:21 EDT

katello commit:  7b40579a7cde2a828ce5fb637a5be1be7bd5e918

New logging option in katello.yml:

 log_level: warn
 log_level_sql: fatal

Allowed log levels: 'debug', 'info', 'warn', 'error', 'fatal'


These can be used within the  'common', 'production', 'development' sections as desired.  The options are commented out by default so the same production/development defaults are used as before.

Comment 3 Og Maciel 2012-09-26 16:19:26 EDT

Verified using:

* candlepin-0.7.8-1.el6cf.noarch
* candlepin-selinux-0.7.8-1.el6cf.noarch
* candlepin-tomcat6-0.7.8-1.el6cf.noarch
* katello-1.1.12-9.el6cf.noarch
* katello-all-1.1.12-9.el6cf.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.8-1.el6cf.noarch
* katello-cli-1.1.8-5.el6cf.noarch
* katello-cli-common-1.1.8-5.el6cf.noarch
* katello-common-1.1.12-9.el6cf.noarch
* katello-configure-1.1.9-4.el6cf.noarch
* katello-glue-candlepin-1.1.12-9.el6cf.noarch
* katello-glue-pulp-1.1.12-9.el6cf.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.1.1-1.el6cf.noarch
* pulp-1.1.12-1.el6cf.noarch
* pulp-common-1.1.12-1.el6cf.noarch
* pulp-selinux-server-1.1.12-1.el6cf.noarch

Comment 5 errata-xmlrpc 2012-12-04 14:43:03 EST

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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html

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