Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1591373 - Flood of deprecation warnings in api.log file
Flood of deprecation warnings in api.log file
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-manila (Show other bugs)
10.0 (Newton)
All All
low Severity low
: z9
: 10.0 (Newton)
Assigned To: Tom Barron
Dustin Schoenbrun
mmurray
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-14 10:52 EDT by Alex Stupnikov
Modified: 2018-09-17 13:00 EDT (History)
6 users (show)

See Also:
Fixed In Version: openstack-manila-3.0.0-12.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, Manila emitted unhelpful warnings about ignored keywords on every wsgi request. As a result, log efficiency was reduced. With this update, the unhelpful warnings no longer appear in logs.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-17 12:59:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
unexpected warning messages (1.39 KB, text/plain)
2018-06-14 10:52 EDT, Alex Stupnikov
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1776947 None None None 2018-06-14 13:36 EDT
OpenStack gerrit 575517 None master: MERGED manila: Remove confusing DB deprecation messages (I95e99b26f416bbf25cfd1c8f7295f3ba6220efb3) 2018-07-06 11:30 EDT
Red Hat Product Errata RHBA-2018:2671 None None None 2018-09-17 13:00 EDT

  None (edit)
Description Alex Stupnikov 2018-06-14 10:52:26 EDT
Created attachment 1451443 [details]
unexpected warning messages

Description of problem:

It looks like manila client is not aligned with manila services. As a result every request generates multiple warning messages about deprecated properties. Those messages are useless, since customer can't fix them.

I believe that we should either update the client, or change severity of those messages to DEBUG.

Please check attached deprecation_warnings.log for additional details.
Comment 1 Tom Barron 2018-06-14 15:25:00 EDT
Thanks for this bug report.  It makes very clear what is wrong with these warnings: they make it sound like the OpenStack user, cloud administrator, or deployer should *do* something to make them go away whereas in fact the only way to make them go away would be to do some re-factoring internal to the manila codebase.  It can't be fixed by changing or updating the client, though it was very reasonable to think that given these messages.

We have proposed changes upstream to get rid of these warnings altogether: https://review.openstack.org/#/c/575517/
Comment 2 Alex Stupnikov 2018-06-15 02:18:09 EDT
Hi Tom. Thank you for detailed feedback and quick reaction. BR, Alex.
Comment 3 Alan Bishop 2018-06-27 09:04:12 EDT
Targeting this for 13z (Tom, please update if you have another target in mind). Upstream patch has merged.
Comment 4 Alex Stupnikov 2018-06-27 09:18:18 EDT
I would like to note that IMO the fix looks good for backporting to RHOSP 10. Since RHOSP 10 will be here for a while, I think it will make sense to backport the patch to it.

BR, Alex.
Comment 5 Tom Barron 2018-06-27 10:02:27 EDT
(In reply to Alex Stupnikov from comment #4)
> I would like to note that IMO the fix looks good for backporting to RHOSP
> 10. Since RHOSP 10 will be here for a while, I think it will make sense to
> backport the patch to it.
> 
> BR, Alex.

I agree.
Comment 14 Alex 2018-09-03 04:01:45 EDT
Hi there,

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field.

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Thanks,
Alex
Comment 16 errata-xmlrpc 2018-09-17 12:59:20 EDT
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/RHBA-2018:2671

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