Bug 1591373
| Summary: | Flood of deprecation warnings in api.log file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alex Stupnikov <astupnik> | ||||
| Component: | openstack-manila | Assignee: | Tom Barron <tbarron> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Dustin Schoenbrun <dschoenb> | ||||
| Severity: | low | Docs Contact: | mmurray | ||||
| Priority: | low | ||||||
| Version: | 10.0 (Newton) | CC: | abishop, amcleod, astupnik, knylande, slinaber, tbarron | ||||
| Target Milestone: | z9 | Keywords: | Triaged, ZStream | ||||
| Target Release: | 10.0 (Newton) | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| 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 16:59:20 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: | |||||||
| Attachments: |
|
||||||
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/ Hi Tom. Thank you for detailed feedback and quick reaction. BR, Alex. Targeting this for 13z (Tom, please update if you have another target in mind). Upstream patch has merged. 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. (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. 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 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 |
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.