[Yahoo-eng-team] [Bug 1713354] Re: oslo.versionedobjects iso8601.is8061.Utc No Longer correct import path in python3

2017-09-05 Thread Hanxi Liu
** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
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/1713354

Title:
  oslo.versionedobjects iso8601.is8061.Utc No Longer correct import path
  in python3

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  In Progress
Status in oslo.versionedobjects:
  In Progress

Bug description:
  iso8601.iso8601 No Longer supports Utc method. Instead iso8601.UTC
  field.

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


[Yahoo-eng-team] [Bug 1654472] Re: funcion sha512.hash() raise AttributeError

2017-01-09 Thread Hanxi Liu
the requirements should be updated.

** Changed in: keystone
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1654472

Title:
  funcion sha512.hash() raise AttributeError

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  2017-01-06 02:45:11.483 | 2017-01-06 10:45:11.480 55501 INFO keystone.cmd.cli 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] Created domain default
  2017-01-06 02:45:11.573 | 2017-01-06 10:45:11.572 55501 INFO keystone.cmd.cli 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] Created project admin
  2017-01-06 02:45:11.649 | 2017-01-06 10:45:11.647 55501 DEBUG 
passlib.registry [req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] 
registered 'sha512_crypt' handler:  register_crypt_handler 
/usr/lib/python2.7/site-packages/passlib/registry.py:284
  2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 CRITICAL keystone 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] AttributeError: type 
object 'sha512_crypt' has no attribute 'hash'
  2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
Traceback (most recent call last):
  2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/usr/bin/keystone-manage", line 10, in 
  2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
sys.exit(main())
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/manage.py", line 45, in main
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
cli.main(argv=sys.argv, config_files=config_files)
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 1283, in main
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
CONF.command.cmd_class.main()
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 380, in main
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
klass.do_bootstrap()
  2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 258, in do_bootstrap
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
'password': self.password
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/manager.py", line 123, in wrapped
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
__ret_val = __f(*args, **kwargs)
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 411, in wrapper
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return f(self, *args, **kwargs)
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 421, in wrapper
  2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return f(self, *args, **kwargs)
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 926, in create_user
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
ref = driver.create_user(user['id'], user)
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/sql/core.py", line 429, in wrapper
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return method(*args, **kwargs)
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/backends/sql.py", line 121, in 
create_user
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
user = utils.hash_user_password(user)
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/utils.py", line 129, in hash_user_password
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return dict(user, password=hash_password(password))
  2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/utils.py", line 135, in hash_password
  2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return passlib.hash.sha512_crypt.hash(
  2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
AttributeError: type object 'sha512_crypt' has no attribute 'hash'
  2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone

To manage notifications about this bug go to:

[Yahoo-eng-team] [Bug 1654472] [NEW] funcion sha512.hash() raise AttributeError

2017-01-05 Thread Hanxi Liu
Public bug reported:

2017-01-06 02:45:11.483 | 2017-01-06 10:45:11.480 55501 INFO keystone.cmd.cli 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] Created domain default
2017-01-06 02:45:11.573 | 2017-01-06 10:45:11.572 55501 INFO keystone.cmd.cli 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] Created project admin
2017-01-06 02:45:11.649 | 2017-01-06 10:45:11.647 55501 DEBUG passlib.registry 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] registered 'sha512_crypt' 
handler:  
register_crypt_handler /usr/lib/python2.7/site-packages/passlib/registry.py:284
2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 CRITICAL keystone 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] AttributeError: type 
object 'sha512_crypt' has no attribute 'hash'
2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
Traceback (most recent call last):
2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/usr/bin/keystone-manage", line 10, in 
2017-01-06 02:45:11.695 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
sys.exit(main())
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/manage.py", line 45, in main
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
cli.main(argv=sys.argv, config_files=config_files)
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 1283, in main
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
CONF.command.cmd_class.main()
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 380, in main
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
klass.do_bootstrap()
2017-01-06 02:45:11.696 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/cmd/cli.py", line 258, in do_bootstrap
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
'password': self.password
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/manager.py", line 123, in wrapped
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
__ret_val = __f(*args, **kwargs)
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 411, in wrapper
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return f(self, *args, **kwargs)
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 421, in wrapper
2017-01-06 02:45:11.697 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return f(self, *args, **kwargs)
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/core.py", line 926, in create_user
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone ref 
= driver.create_user(user['id'], user)
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/sql/core.py", line 429, in wrapper
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return method(*args, **kwargs)
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/identity/backends/sql.py", line 121, in 
create_user
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone user 
= utils.hash_user_password(user)
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/utils.py", line 129, in hash_user_password
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return dict(user, password=hash_password(password))
2017-01-06 02:45:11.698 | 2017-01-06 10:45:11.649 55501 TRACE keystone   File 
"/opt/stack/keystone/keystone/common/utils.py", line 135, in hash_password
2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
return passlib.hash.sha512_crypt.hash(
2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone 
AttributeError: type object 'sha512_crypt' has no attribute 'hash'
2017-01-06 02:45:11.699 | 2017-01-06 10:45:11.649 55501 TRACE keystone

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1654472

Title:
  funcion sha512.hash() raise AttributeError

Status in OpenStack Identity (keystone):
  New

Bug description:
  2017-01-06 02:45:11.483 | 2017-01-06 10:45:11.480 55501 INFO keystone.cmd.cli 
[req-666b53bd-ef9b-4eb3-be09-2c1fa5483162 - - - - -] Created domain default
  2017-01-06 

[Yahoo-eng-team] [Bug 1590608] Re: Services should use http_proxy_to_wsgi middleware

2016-10-10 Thread Hanxi Liu
** Also affects: panko
   Importance: Undecided
   Status: New

** Changed in: panko
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1590608

Title:
  Services should use http_proxy_to_wsgi middleware

Status in Aodh:
  Fix Released
Status in Barbican:
  New
Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in neutron:
  In Progress
Status in Panko:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress

Bug description:
  It's a common problem when putting a service behind a load balancer to
  need to forward the Protocol and hosts of the original request so that
  the receiving service can construct URLs to the loadbalancer and not
  the private worker node.

  Most services have implemented some form of secure_proxy_ssl_header =
  HTTP_X_FORWARDED_PROTO handling however exactly how this is done is
  dependent on the service.

  oslo.middleware provides the http_proxy_to_wsgi middleware that
  handles these headers and the newer RFC7239 forwarding header and
  completely hides the problem from the service.

  This middleware should be adopted by all services in preference to
  their own HTTP_X_FORWARDED_PROTO handling.

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


[Yahoo-eng-team] [Bug 1280105] Re: urllib/urllib2 is incompatible for python 3

2016-09-27 Thread Hanxi Liu
** Also affects: swift
   Importance: Undecided
   Status: New

** No longer affects: swift

** Also affects: swift
   Importance: Undecided
   Status: New

** Changed in: swift
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1280105

Title:
  urllib/urllib2  is incompatible for python 3

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Fuel for OpenStack:
  Fix Released
Status in Glance:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Committed
Status in neutron:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in refstack:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  New
Status in tacker:
  In Progress
Status in tempest:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in Zuul:
  In Progress

Bug description:
  urllib/urllib2  is incompatible for python 3

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


[Yahoo-eng-team] [Bug 1517839] Re: Make CONF.set_override with parameter enforce_type=True by default

2016-09-04 Thread Hanxi Liu
** Also affects: gnocchi
   Importance: Undecided
   Status: New

** Changed in: gnocchi
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1517839

Title:
  Make CONF.set_override with parameter enforce_type=True by default

Status in Ceilometer:
  New
Status in Cinder:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  Fix Released
Status in Freezer:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in Gnocchi:
  New
Status in heat:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Won't Fix
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.config:
  In Progress
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Released
Status in tacker:
  In Progress
Status in watcher:
  Fix Released

Bug description:
  1. Problems :
     oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
     By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
     override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
     In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
     parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.

     [1]
  https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173

  2. Proposal
     1) Fix violations when enforce_type=True in each project.

    2) Make method CONF.set_override with  enforce_type=True by default
  in oslo_config

   You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

  3. How to find violations in your projects.

     1. Run tox -e py27

     2. then modify oslo.config with enforce_type=True
    cd .tox/py27/lib64/python2.7/site-packages/oslo_config
    edit cfg.py with enforce_type=True

  -def set_override(self, name, override, group=None, enforce_type=False):
  +def set_override(self, name, override, group=None, enforce_type=True):

    3. Run tox -e py27 again, you will find violations.

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


[Yahoo-eng-team] [Bug 1586268] Re: Unit test: self.assertNotEqual in unit.test_base.BaseTest.test_eq does not work in PY2

2016-08-23 Thread Hanxi Liu
** Also affects: panko
   Importance: Undecided
   Status: New

** Changed in: panko
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** Also affects: gnocchi
   Importance: Undecided
   Status: New

** Changed in: gnocchi
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586268

Title:
  Unit test: self.assertNotEqual in  unit.test_base.BaseTest.test_eq
  does not work in PY2

Status in Ceilometer:
  Fix Released
Status in daisycloud-core:
  New
Status in Gnocchi:
  New
Status in heat:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in Panko:
  New
Status in python-barbicanclient:
  New
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-glanceclient:
  In Progress
Status in python-heatclient:
  Fix Released
Status in python-smaugclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-muranoclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in tempest:
  In Progress

Bug description:
  Version: master(20160527)

  In case cinderclient.tests.unit.test_base.BaseTest.test_eq 
self.assertNotEqual does not work.
  Class base.Resource defines __eq__() built-in function, but does not define 
__ne__() built-in function, so self.assertEqual works but self.assertNotEqual 
does not work at all in this test case.

  steps:
  1 Clone code of python-cinderclient from master.
  2 Modify the case of unit test: cinderclient/tests/unit/test_base.py
    line50--line62.
  def test_eq(self):
  # Two resources with same ID: never equal if their info is not equal
  r1 = base.Resource(None, {'id': 1, 'name': 'hi'})
  r2 = base.Resource(None, {'id': 1, 'name': 'hello'})
  self.assertNotEqual(r1, r2)

  # Two resources with same ID: equal if their info is equal
  r1 = base.Resource(None, {'id': 1, 'name': 'hello'})
  r2 = base.Resource(None, {'id': 1, 'name': 'hello'})
  # self.assertEqual(r1, r2)
  self.assertNotEqual(r1, r2)

  # Two resoruces of different types: never equal
  r1 = base.Resource(None, {'id': 1})
  r2 = volumes.Volume(None, {'id': 1})
  self.assertNotEqual(r1, r2)

  # Two resources with no ID: equal if their info is equal
  r1 = base.Resource(None, {'name': 'joe', 'age': 12})
  r2 = base.Resource(None, {'name': 'joe', 'age': 12})
  # self.assertEqual(r1, r2)
  self.assertNotEqual(r1, r2)

     Modify self.assertEqual(r1, r2) to self.assertNotEqual(r1, r2).

  3 Run unit test, and return success.

  After that, I make a test:

  class Resource(object):
  def __init__(self, person):
  self.person = person

  def __eq__(self, other):
  return self.person == other.person

  r1 = Resource("test")
  r2 = Resource("test")
  r3 = Resource("test_r3")
  r4 = Resource("test_r4")

  print r1 != r2
  print r1 == r2
  print r3 != r4
  print r3 == r4

  The result is :
  True
  True
  True
  False

  Whether r1 is precisely the same to r2 or not, self.assertNotEqual(r1,
  r2) return true.So I think self.assertNotEqual doesn't work at all in
  python2 and  should be modified.

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


[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated

2016-08-22 Thread Hanxi Liu
** Also affects: panko
   Importance: Undecided
   Status: New

** Changed in: panko
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** No longer affects: panko

-- 
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 networking-arista:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-cisco:
  In Progress
Status in networking-fujitsu:
  Fix Released
Status in networking-odl:
  In Progress
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


[Yahoo-eng-team] [Bug 1613542] Re: tempest.conf doesn't contain $project in [service_available] section

2016-08-22 Thread Hanxi Liu
** Also affects: gnocchi
   Importance: Undecided
   Status: New

** Changed in: gnocchi
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1613542

Title:
  tempest.conf doesn't contain $project in [service_available] section

Status in Aodh:
  Fix Released
Status in Ceilometer:
  In Progress
Status in ec2-api:
  In Progress
Status in Gnocchi:
  New
Status in OpenStack Identity (keystone):
  In Progress
Status in Magnum:
  Fix Released

Bug description:
  When generating the tempest conf, the tempest plugins need to register the 
config options.
  But for the [service_available] section, ceilometer (and the other mentioned 
projects) doesn't register any value so it's missng in the tempest sample 
config.

  Steps to reproduce:

  $ tox -egenconfig
  $ source .tox/genconfig/bin/activate
  $ oslo-config-generator --config-file 
.tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf
 --output-file tempest.conf.sample

  Now check the [service_available] section from tempest.conf.sample

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


[Yahoo-eng-team] [Bug 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints

2016-08-22 Thread Hanxi Liu
** No longer affects: aodh

** No longer affects: gnocchi

** No longer affects: panko

** No longer affects: python-ceilometerclient

** No longer affects: python-gnocchiclient

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1614361

Title:
  tox.ini needs to be updated as openstack infra now supports upper
  constraints

Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in Glance:
  New
Status in heat:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in Ironic Inspector:
  New
Status in Mistral:
  In Progress
Status in Murano:
  New
Status in neutron:
  New
Status in octavia:
  New
Status in openstack-ansible:
  New
Status in python-muranoclient:
  New
Status in tacker:
  New
Status in OpenStack DBaaS (Trove):
  New
Status in vmware-nsx:
  New
Status in zaqar:
  In Progress
Status in Zaqar-ui:
  Fix Released

Bug description:
  Openstack infra now supports upper constraints for releasenotes, cover, venv 
targets.
  tox.ini uses install_command for these targets, which can now be safely 
removed.
  Reference for mail that details this support: 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html

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


[Yahoo-eng-team] [Bug 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints

2016-08-22 Thread Hanxi Liu
** Also affects: python-ceilometerclient
   Importance: Undecided
   Status: New

** Changed in: python-ceilometerclient
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** Also affects: panko
   Importance: Undecided
   Status: New

** Changed in: panko
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** Also affects: gnocchi
   Importance: Undecided
   Status: New

** Changed in: gnocchi
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** Also affects: python-gnocchiclient
   Importance: Undecided
   Status: New

** Changed in: python-gnocchiclient
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

** Also affects: aodh
   Importance: Undecided
   Status: New

** Changed in: aodh
 Assignee: (unassigned) => Hanxi Liu (hanxi-liu)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1614361

Title:
  tox.ini needs to be updated as openstack infra now supports upper
  constraints

Status in Aodh:
  New
Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in Glance:
  New
Status in Gnocchi:
  New
Status in heat:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in Ironic Inspector:
  New
Status in Mistral:
  In Progress
Status in Murano:
  New
Status in neutron:
  New
Status in octavia:
  New
Status in openstack-ansible:
  New
Status in Panko:
  New
Status in python-ceilometerclient:
  New
Status in python-gnocchiclient:
  New
Status in python-muranoclient:
  New
Status in tacker:
  New
Status in OpenStack DBaaS (Trove):
  New
Status in vmware-nsx:
  New
Status in zaqar:
  In Progress
Status in Zaqar-ui:
  Fix Released

Bug description:
  Openstack infra now supports upper constraints for releasenotes, cover, venv 
targets.
  tox.ini uses install_command for these targets, which can now be safely 
removed.
  Reference for mail that details this support: 
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html

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