Bug 1032101

Summary:	Default settings cause masses of deprecation warnings in httpd error log
Product:	[Fedora] Fedora EPEL	Reporter:	Thomas Widhalm <thomas.widhalm>
Component:	graphite-web	Assignee:	Jonathan Steffan <jonathansteffan>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	albert.mkhitaryan, jonathansteffan, piotr1212
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 15:55:22 UTC	Type:	Bug
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:	1284264
Bug Blocks:

Description Thomas Widhalm 2013-11-19 14:46:56 UTC

Description of problem:
Some settings in /usr/lib/python2.6/site-packages/graphite/app_settings.py from the graphite-web package cause the following messages to appear in /var/log/httpd/error_log (even though the graphite-web vhost uses another error log) whenever one navigates to the graphite-web vhost.

[Tue Nov 19 15:00:52 2013] [error] /usr/lib/python2.6/site-packages/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
[Tue Nov 19 15:00:52 2013] [error]   "use STATIC_URL instead.", DeprecationWarning)
[Tue Nov 19 15:00:52 2013] [error] /usr/lib/python2.6/site-packages/django/core/cache/__init__.py:82: DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES instead.
[Tue Nov 19 15:00:52 2013] [error]   DeprecationWarning


Version-Release number of selected component (if applicable):
Name        : graphite-web
Arch        : noarch
Version     : 0.9.12
Release     : 5.el6
Size        : 8.9 M
Repo        : installed
From repo   : epel


How reproducible:

refer to the following steps

Steps to Reproduce:
1. Install graphite-web
2. set dns to point graphite-web to the host you installed on
3. browse to http://graphite-web
4. look at /var/log/httpd/error_log

Actual results:
error_log contains deprecation warnings

Expected results:
No deprecation warnings due to an updates configuration file

Additional info:
There are 2 Log entries per step one takes on the graphite web interface so the logs get swamped with log entries.

Comment 1 Jonathan Steffan 2014-11-22 23:21:04 UTC

Jamie,

What are your thoughts on this? Should we just patch in the new variables?

Comment 2 Jamie Nguyen 2014-11-24 19:56:43 UTC

(In reply to Jonathan Steffan from comment #1)
> What are your thoughts on this? Should we just patch in the new variables?

We should probably patch, as nobody likes thousands of deprecation warnings. Just need to make sure we test the changes.

Comment 3 Ben Cotton 2020-11-05 16:53:52 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-05 16:56:28 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-30 15:55:22 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.