Reviewed:  https://review.openstack.org/265590
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=0a718818f4d7f4bc1ab745eb3081321ef6cf9a3a
Submitter: Jenkins
Branch:    master

commit 0a718818f4d7f4bc1ab745eb3081321ef6cf9a3a
Author: LiuNanke <nanke....@easystack.cn>
Date:   Sun Jan 10 04:22:34 2016 +0800

    Replace deprecated library function os.popen() with subprocess
    
    os.popen() is deprecated since version 2.6. Resolved with use of
    subprocess module.
    Closes-bug: #1529836
    
    Change-Id: I61cf2ff6ef939b97c1c70325e15b89a47e5646e4


** Changed in: neutron
       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/1529836

Title:
  Fix deprecated library function (os.popen()).

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Sahara:
  In Progress
Status in senlin:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1529836/+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

Reply via email to