Bug 1118578

Summary:	[RFE][glance]: Refactoring Glance Logging
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-glance	Assignee:	Flavio Percoco <fpercoco>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ddomingo, eglynn, fpercoco, markmc, scohen, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-glance-2015.1.0-6.el7ost	Doc Type:	Enhancement
Doc Text:	The Image Service now features improved logging, providing better information to users. In addition, logs have been stripped of any sensitive information, and use the appropriate logging levels for messages. This change is only visible to operators.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:13:04 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:

Description RHOS Integration 2014-07-11 04:10:22 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging.

Description:

I would like to see whole Glance codebase revisited and the logging changed to use appropriate logging level and reflect the translation functions to those levels as well. This would be also good opportunity to ensure that we have no logging left that would write sensitive information like URIs and credentials to logfiles.

Specification URL (additional information):

https://github.com/openstack/glance-specs/blob/master/specs/juno/refactoring-glance-logging.rst

Comment 9 errata-xmlrpc 2015-08-05 13:13:04 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/RHEA-2015:1548