logs are full of manila-scheduler: Arguments dropped when creating context: {u'user': None, u'tenant': None}

Bug #1607444 reported by DeepthiGaddam
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Low
Arne Wiebalck

Bug Description

Our logs are full of
manila-scheduler: Arguments dropped when creating context: {u'user': None, u'tenant': None}
messages.

Default log level was WARNING. Can't change the manila_context logging level to ERRROR in manila.conf file.

I see that.. this bug was fixed in Cinder

Bug #1329156, Lots of cinder.context warning in scheduler log Edit

Can some-one fix this issue in Manila too. It is affecting our project's logging service. Moreover it is very hard to debug the logs too.

Thanks

description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.openstack.org/390773

Changed in manila:
assignee: nobody → Arne Wiebalck (arne-wiebalck)
status: New → In Progress
Changed in manila:
importance: Undecided → Low
milestone: none → ocata-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/390773
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=38c1eaede52e800b2289afc38146b1120be82ddf
Submitter: Jenkins
Branch: master

commit 38c1eaede52e800b2289afc38146b1120be82ddf
Author: Arne Wiebalck <email address hidden>
Date: Wed Oct 26 10:29:40 2016 +0200

    Remove warnings for dropped context arguments

    This patch removes the warning messages for dropped arguments upon
    context setup. They are of limited use and dropping them should
    increase the readability of the logs.

    Change-Id: I8003dd576a575be4d87e69ef5459009eeb15fabe
    Closes-Bug: #1607444

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 4.0.0.0b1

This issue was fixed in the openstack/manila 4.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.