Reviewed: https://review.openstack.org/396256
Committed:
https://git.openstack.org/cgit/openstack/networking-arista/commit/?id=1b01eb60a45596bc731e86e9bede5039a8d0db6e
Submitter: Jenkins
Branch: master
commit 1b01eb60a45596bc731e86e9bede5039a8d0db6e
Author: Mark McClain <m...@mcclain.xyz>
Date: Thu Nov 10 09:28:49 2016 -0500
use LOG.warning instead of LOG.warn
Minor clean-up to convert usage of deprecated LOG.warn method to
LOG.warning.
Change-Id: I597d44ac0d48571ffb29d55761fe2aff5a518302
Closes-Bug: #1508442
** Changed in: networking-arista
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1508442
Title:
LOG.warn is deprecated
Status in anvil:
In Progress
Status in Aodh:
Fix Released
Status in Astara:
Fix Released
Status in Barbican:
Fix Released
Status in bilean:
Fix Released
Status in Ceilometer:
Fix Released
Status in cloud-init:
In Progress
Status in cloudkitty:
Fix Released
Status in congress:
Fix Released
Status in Designate:
Fix Released
Status in django-openstack-auth:
Fix Released
Status in django-openstack-auth-kerberos:
In Progress
Status in DragonFlow:
Fix Released
Status in ec2-api:
Fix Released
Status in Evoque:
In Progress
Status in Freezer:
In Progress
Status in gce-api:
Fix Released
Status in Glance:
In Progress
Status in Gnocchi:
Fix Released
Status in heat:
Fix Released
Status in heat-cfntools:
Fix Released
Status in OpenStack Identity (keystone):
Fix Released
Status in KloudBuster:
Fix Released
Status in kolla:
Fix Released
Status in Magnum:
Fix Released
Status in Manila:
Fix Released
Status in masakari:
Fix Released
Status in Mistral:
In Progress
Status in Monasca:
New
Status in networking-arista:
Fix Released
Status in networking-calico:
In Progress
Status in networking-cisco:
In Progress
Status in networking-fujitsu:
Fix Released
Status in networking-odl:
Fix Committed
Status in networking-ofagent:
In Progress
Status in networking-plumgrid:
In Progress
Status in networking-powervm:
Fix Released
Status in networking-vsphere:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in nova-powervm:
Fix Released
Status in nova-solver-scheduler:
In Progress
Status in octavia:
Fix Released
Status in openstack-ansible:
Fix Released
Status in oslo.cache:
Fix Released
Status in oslo.middleware:
New
Status in Packstack:
Fix Released
Status in python-dracclient:
Fix Released
Status in python-magnumclient:
Fix Released
Status in RACK:
In Progress
Status in python-watcherclient:
In Progress
Status in Rally:
Fix Released
Status in OpenStack Search (Searchlight):
Fix Released
Status in senlin:
Fix Committed
Status in shaker:
Fix Released
Status in Solum:
Fix Released
Status in tacker:
Fix Released
Status in tempest:
Fix Released
Status in tripleo:
Fix Released
Status in trove-dashboard:
Fix Released
Status in Vitrage:
Fix Committed
Status in watcher:
Fix Released
Status in zaqar:
Fix Released
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/anvil/+bug/1508442/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
