Add hacking check to ensure LOG.warn is not used

Bug #1605711 reported by yatin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
yatin
OpenStack Backup/Restore and DR (Freezer)
In Progress
Undecided
yatin
Vitrage
In Progress
Undecided
yatin
senlin
Fix Released
Undecided
yatin

Bug Description

LOG.warn is deprecated, instead LOG.warning should be used.
Add hacking check to ensure LOG.warn is not used.

Currently LOG.warn is replaced with LOG.warning in bug Fix of: #1508442.

yatin (yatinkarel)
Changed in senlin:
assignee: nobody → yatin (yatinkarel)
yatin (yatinkarel)
Changed in senlin:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to senlin (master)

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

yatin (yatinkarel)
Changed in magnum:
assignee: nobody → yatin (yatinkarel)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

yatin (yatinkarel)
Changed in vitrage:
assignee: nobody → yatin (yatinkarel)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to vitrage (master)

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

yatin (yatinkarel)
Changed in freezer:
assignee: nobody → yatin (yatinkarel)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to senlin (master)

Reviewed: https://review.openstack.org/346418
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=91341e6f744bff0a09a9992f44e6cc34a9c789cd
Submitter: Jenkins
Branch: master

commit 91341e6f744bff0a09a9992f44e6cc34a9c789cd
Author: yatinkarel <email address hidden>
Date: Sat Jul 23 20:43:12 2016 +0530

    Add hacking check to ensure LOG.warn is not used

    LOG.warn is replaced with LOG.warning in review:
    https://review.openstack.org/#/c/343214/. But use of
    LOG.warn should not happen again.
    So added hacking check to ensure LOG.warn is not used

    Change-Id: Ice650ba14386b136e72d1b91c0411b390ebfd429
    Closes-Bug: #1605711

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

Reviewed: https://review.openstack.org/346516
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=5c2fc0b392adb4db2605ba95460cb3910ad94fa1
Submitter: Jenkins
Branch: master

commit 5c2fc0b392adb4db2605ba95460cb3910ad94fa1
Author: yatinkarel <email address hidden>
Date: Sun Jul 24 18:23:23 2016 +0530

    Added hacking check to ensure LOG.warn is not used

    LOG.warn is deprecated. To ensure it is not used later
    added hacking check.

    Change-Id: Iadd1d4f4588c9d47baefd685a97a73c8b1aee987
    Closes-Bug: #1605711

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

This issue was fixed in the openstack/magnum 3.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/senlin 2.0.0.0b3

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on freezer (master)

Change abandoned by yatin (<email address hidden>) on branch: master
Review: https://review.openstack.org/346530
Reason: As stated by Erno Kuvaja: This is not required.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on vitrage (master)

Change abandoned by yatin (<email address hidden>) on branch: master
Review: https://review.openstack.org/346522
Reason: Abandoned it because of no review for long.

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.