Red Hat Bugzilla – Bug 1264569
Log_level Deprecation warning in log
Last modified: 2015-12-08 08:31:48 EST
Description of problem: Deprecation message in log Version-Release number of selected component (if applicable): 5.5.0.1-alpha1.20150915151429_2230bd4 How reproducible: 100% Steps to Reproduce: 1. Startup CloudForms 2. 3. Actual results: Error in log Expected results: No error Additional info: evm.log excerpt: [----] I, [2015-09-17T05:25:56.716255 #13609:d19994] INFO -- : MIQ(Vmdb::Loggers.apply_config) Log level for vim.log has been changed to [WARN] DEPRECATION WARNING: You did not specify a `log_level` in `production.rb`. Currently, the default value for `log_level` is `:info` for the production environment and `:debug` in all other environments . In Rails 5 the default value will be unified to `:debug` across all environments. To preserve the current setting, add the following line to your `production.rb`: config.log_level = :info . (called from block in tsort_each at /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226)
https://github.com/ManageIQ/manageiq/pull/4449
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f875c1ebf4f37830616e133a2e682d339216e287 commit f875c1ebf4f37830616e133a2e682d339216e287 Author: Nick Carboni <ncarboni@redhat.com> AuthorDate: Mon Sep 21 09:19:04 2015 -0400 Commit: Nick Carboni <ncarboni@redhat.com> CommitDate: Mon Sep 21 09:19:04 2015 -0400 Explicitly specified log level for production Currently the default for production logging is info, but in rails 5 all defaults will be debug. This also prevents lots of deprecation warning messages. https://bugzilla.redhat.com/show_bug.cgi?id=1264569 config/environments/production.rb | 1 + 1 file changed, 1 insertion(+)
Verified in 5.5.0.7-beta1.3
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/RHSA-2015:2551