yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #44051
[Bug 1508442] Re: LOG.warn is deprecated
Reviewed: https://review.openstack.org/263562
Committed: https://git.openstack.org/cgit/openstack/ironic-python-agent/commit/?id=dcdb06d812e1eee1506aa7e99d0182bc41e21b82
Submitter: Jenkins
Branch: master
commit dcdb06d812e1eee1506aa7e99d0182bc41e21b82
Author: Kan <kansks@xxxxxxxxxx>
Date: Tue Jan 5 05:36:34 2016 +0000
Replace deprecated LOG.warn with LOG.warning
Change-Id: I0ca31eac70afaccda73e7819c582af0b226b8442
Closes-Bug: #1508442
** Changed in: ironic-python-agent
Status: Fix Committed => 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/1508442
Title:
LOG.warn is deprecated
Status in Aodh:
In Progress
Status in Ceilometer:
In Progress
Status in cloud-init:
New
Status in cloudkitty:
In Progress
Status in Designate:
In Progress
Status in Glance:
In Progress
Status in Gnocchi:
In Progress
Status in heat:
Fix Released
Status in Ironic:
Fix Released
Status in Ironic Inspector:
Fix Released
Status in ironic-lib:
Fix Committed
Status in ironic-python-agent:
Fix Released
Status in OpenStack Identity (keystone):
In Progress
Status in kolla:
Fix Released
Status in Magnum:
Fix Released
Status in Manila:
In Progress
Status in networking-cisco:
In Progress
Status in neutron:
In Progress
Status in nova-powervm:
Fix Released
Status in octavia:
In Progress
Status in openstack-ansible:
In Progress
Status in oslo.cache:
In Progress
Status in oslo.privsep:
In Progress
Status in Packstack:
In Progress
Status in python-magnumclient:
Fix Released
Status in Solum:
In Progress
Status in tempest:
In Progress
Status in tripleo:
In Progress
Status in tuskar:
In Progress
Status in zaqar:
In Progress
Bug description:
LOG.warn is deprecated in Python 3 [1] . But it still used in a few
places, non-deprecated LOG.warning should be used instead.
Note: If we are using logger from oslo.log, warn is still valid [2],
but I agree we can switch to LOG.warning.
[1]https://docs.python.org/3/library/logging.html#logging.warning
[2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1508442/+subscriptions