← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1532053] Re: No handlers could be found for logger "oslo_reports.guru_meditation_report"

 

Reviewed:  https://review.openstack.org/265041
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c170765132d6f24b08a4e40274df589813cebf85
Submitter: Jenkins
Branch:    master

commit c170765132d6f24b08a4e40274df589813cebf85
Author: John Davidge <jodavidg@xxxxxxxxx>
Date:   Mon Feb 8 14:57:25 2016 -0800

    Fix logging error for Guru Meditation Report
    
    Currently, invoking any of the commands under neutron/cmd will trigger a
    "No handlers could be found" error for Guru Meditation Report. This is
    interupting the notify.sh script that is called by dibbler-client during the
    IPv6 Prefix Delegation workflow.
    
    This patch adds a logging handler to __init__.py to prevent the error.
    
    Without the error message being thrown, neutron-pd-notify is once again
    able to complete successfully when called by dibbler-client.
    
    Change-Id: Iac3162f6b7e968c2f11fd8ef2a6e275242fb21ff
    Closes-Bug: 1532053


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1532053

Title:
  No handlers could be found for logger
  "oslo_reports.guru_meditation_report"

Status in neutron:
  Fix Released

Bug description:
  Support for Guru Meditation Report was merged on December 9th by [1].
  Since then running anything found in neutron/cmd produces the error:

  No handlers could be found for logger
  "oslo_reports.guru_meditation_report"

  This is causing the neutron-pd-notify command to fail when called by
  the dibbler-client process, and could be causing other as-yet
  undiscovered issues.

  The issue is solved by moving the importing an invoking of guru
  meditation report out of __init__ and into the individual files of
  neutron/cmd, where logging is handled correctly.

  [1] https://review.openstack.org/#/c/250487

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1532053/+subscriptions


References