zaqar

Fix improperly LOG using in Zaqar

Bug #1543563 reported by wanghao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
Undecided
wanghao

Bug Description

In zaqar, there are some improperly log using in code tree. Like in some place, should use LOG.exception not LOG.error, repeat log calling, etc.

Those could be optimized for better code.

wanghao (wanghao749)
Changed in zaqar:
assignee: nobody → wanghao (wanghao749)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zaqar (master)

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

Changed in zaqar:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar (master)

Reviewed: https://review.openstack.org/277812
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=1685f5853aa9b6a3959df9773acc952db814a15c
Submitter: Jenkins
Branch: master

commit 1685f5853aa9b6a3959df9773acc952db814a15c
Author: wanghao <email address hidden>
Date: Tue Feb 9 20:47:12 2016 +0800

    Fix improperly LOG using in Zaqar

    In zaqar, there are some improperly log using in code tree. Like in some
    place, should use LOG.exception not LOG.error, repeat log calling, etc.

    Those could be optimized for better code.

    Change-Id: I99b830c4db4f2b9449cad713f37474f5ecbce05e
    Closes-Bug: #1543563

Changed in zaqar:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/zaqar 2.0.0.0b3

This issue was fixed in the openstack/zaqar 2.0.0.0b3 development milestone.

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

Other bug subscribers

Remote bug watches

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