← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1596829] Re: String interpolation should be delayed at logging calls

 

Reviewed:  https://review.openstack.org/428686
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=34a3aa0ba8783c5cc191fff730a164d377d4c89f
Submitter: Jenkins
Branch:    master

commit 34a3aa0ba8783c5cc191fff730a164d377d4c89f
Author: Gábor Antal <antal@xxxxxxxxxxxxxxx>
Date:   Tue Mar 28 16:47:28 2017 +0200

    Handle log message interpolation by the logger
    
    According to OpenStack Guideline[1], logged string message should be
    interpolated by the logger.
    
    [1]: http://docs.openstack.org/developer/oslo.i18n/guidelines.html#adding-variables-to-log-messages
    Change-Id: I51f50935f1eeffe4960562d6309dfdf05814e595
    Closes-Bug: #1596829


** Changed in: horizon
       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/1596829

Title:
  String interpolation should be delayed at logging calls

Status in congress:
  Fix Released
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in masakari:
  Fix Released
Status in networking-vsphere:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in os-brick:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in Glance Client:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in python-troveclient:
  In Progress
Status in Sahara:
  New
Status in senlin:
  Invalid

Bug description:
  String interpolation should be delayed to be handled by the logging
  code, rather than being done at the point of the logging call.

  Wrong: LOG.debug('Example: %s' % 'bad')
  Right: LOG.debug('Example: %s', 'good')

  See the following guideline.

  * http://docs.openstack.org/developer/oslo.i18n/guidelines.html
  #adding-variables-to-log-messages

  The rule for it should be added to hacking checks.

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


References