Bug 1271941
| Summary: | Warning Cinder scheduler context | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Shinobu KINJO <skinjo> |
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> |
| Status: | CLOSED NOTABUG | QA Contact: | nlevinki <nlevinki> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 (RHEL 7) | CC: | eharney, sgotliv, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-19 06:42:18 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: | |||
Cinder stopped printing these messages in Juno (6.0). (In reply to Sergey Gotliv from comment #2) > Cinder stopped printing these messages in Juno (6.0). Will this fix be (able to be) backported to Icehouse based OSP? |
Description of problem: A bunch of noisy messages from cinder coming from: /usr/lib/python2.7/site-packages/cinder/context.py Message is: "opme1os205 <148>Oct 12 15:45:57 opme1os205 journal: cinder-scheduler 2015-10-12 15:45:57.192 53795 WARNING cinder.context [-] Arguments dropped when creating context: {'user': None, 'tenant': None, 'user_identity': u'- - - - -'}" This is because of: 62 if kwargs: 63 LOG.warn(_('Arguments dropped when creating context: %s') % 64 str(kwargs)) Especially: kwargs Based on explanation in context.py, this param is not necessary here. 59 :param kwargs: Extra arguments that might be present, but we ignore 60 because they possibly came in from older rpc messages. Question from my side, Why do we still keep that __if__ block? I think that there is no dependencies with that block. So we should be able to simply remove those 3 lines. What do you think? If I've missed anything, point it out to me. Shinobu Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: