[Yahoo-eng-team] [Bug 1810490] [NEW] wrong link of gabbits
Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: The "gabbits" url is incorrect at https://docs.openstack.org/placement/latest/#rest-api - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. The correct is http://git.openstack.org/cgit/openstack/placement/tree/placement/tests/functional/gabbits If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 0.0.1.dev10886 on 2018-11-19 19:26:28 SHA: 9d42491910e66ecd15767238bb617ed5984283f2 Source: https://git.openstack.org/cgit/openstack/placement/tree/doc/source/index.rst URL: https://docs.openstack.org/placement/latest/ ** Affects: nova Importance: Undecided Assignee: lei zhang (zhang-lei) Status: In Progress ** Tags: doc ** Changed in: nova Assignee: (unassigned) => lei zhang (zhang-lei) -- 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/1810490 Title: wrong link of gabbits Status in OpenStack Compute (nova): In Progress Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: The "gabbits" url is incorrect at https://docs.openstack.org/placement/latest/#rest-api - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. The correct is http://git.openstack.org/cgit/openstack/placement/tree/placement/tests/functional/gabbits If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 0.0.1.dev10886 on 2018-11-19 19:26:28 SHA: 9d42491910e66ecd15767238bb617ed5984283f2 Source: https://git.openstack.org/cgit/openstack/placement/tree/doc/source/index.rst URL: https://docs.openstack.org/placement/latest/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1810490/+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 1547098] [NEW] namespace not updated on namespace properties change
Public bug reported: When namespace properties are updated using metadata api, the updated_at time of namespace doesn't change. It's not a valid result, updated time of namespace should reflect changes to properties. It causes problems for Searchlight. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1547098 Title: namespace not updated on namespace properties change Status in Glance: New Bug description: When namespace properties are updated using metadata api, the updated_at time of namespace doesn't change. It's not a valid result, updated time of namespace should reflect changes to properties. It causes problems for Searchlight. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1547098/+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 1529836] Re: Fix deprecated library function (os.popen()).
** Also affects: senlin Importance: Undecided Status: New ** Changed in: senlin Status: New => In Progress ** Changed in: senlin Assignee: (unassigned) => lei zhang (zhang-lei) -- 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): In Progress Status in Manila: Fix Released Status in Murano: In Progress Status in neutron: In Progress Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: In Progress Status in python-keystoneclient: In Progress Status in senlin: In Progress Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress Status in zaqar: In Progress 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
[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).
** Changed in: murano Assignee: lei zhang (zhang-lei) => (unassigned) ** No longer affects: zaqar ** No longer affects: heat -- 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 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 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
[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Status: New => In Progress ** Changed in: zaqar Assignee: (unassigned) => lei zhang (zhang-lei) ** Also affects: murano Importance: Undecided Status: New ** Changed in: murano Status: New => In Progress ** Changed in: murano Assignee: (unassigned) => lei zhang (zhang-lei) ** Also affects: heat Importance: Undecided Status: New ** Changed in: heat Status: New => In Progress ** Changed in: heat Assignee: (unassigned) => lei zhang (zhang-lei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. 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): In Progress Status in Manila: Fix Released Status in Murano: In Progress Status in neutron: In Progress Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: In Progress Status in python-keystoneclient: In Progress Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress Status in zaqar: In Progress 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
[Yahoo-eng-team] [Bug 1529836] Re: Fix deprecated library function (os.popen()).
** Also affects: ceilometer Importance: Undecided Status: New ** Changed in: ceilometer Status: New => In Progress ** Changed in: ceilometer Assignee: (unassigned) => lei zhang (zhang-lei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. 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 OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in Manila: Fix Released Status in neutron: In Progress Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: In Progress Status in python-keystoneclient: In Progress Status in OpenStack Object Storage (swift): In Progress Status in tempest: In Progress 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
[Yahoo-eng-team] [Bug 1508442] Re: LOG.warn is deprecated
** Also affects: networking-vsphere Importance: Undecided Status: New ** Changed in: networking-vsphere Status: New => In Progress ** Changed in: networking-vsphere Assignee: (unassigned) => lei zhang (zhang-lei) -- 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: In Progress Status in cloudkitty: In Progress Status in Designate: In Progress Status in DragonFlow: 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 networking-odl: In Progress Status in networking-ofagent: In Progress Status in networking-vsphere: 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 -- 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
** Also affects: ceilometer Importance: Undecided Status: New ** Changed in: ceilometer Status: New => In Progress ** Changed in: ceilometer Assignee: (unassigned) => lei zhang (zhang-lei) -- 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 cloudkitty: In Progress Status in Designate: In Progress Status in Glance: In Progress Status in Gnocchi: In Progress Status in heat: In Progress Status in Ironic: Fix Released Status in Ironic Inspector: Fix Released Status in ironic-lib: Fix Committed Status in ironic-python-agent: Fix Committed Status in OpenStack Identity (keystone): In Progress Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: 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: In Progress 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 -- 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
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Assignee: (unassigned) => lei zhang (zhang-lei) -- 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: In Progress Status in Ironic: Fix Released Status in Ironic Inspector: Fix Released Status in ironic-lib: Fix Committed Status in ironic-python-agent: Fix Committed Status in OpenStack Identity (keystone): In Progress Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: 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: In Progress 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 -- 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
** Also affects: networking-ofagent Importance: Undecided Status: New ** Changed in: networking-ofagent Status: New => In Progress ** Changed in: networking-ofagent Assignee: (unassigned) => lei zhang (zhang-lei) -- 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: In Progress Status in cloudkitty: In Progress Status in Designate: In Progress Status in DragonFlow: 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 networking-ofagent: 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 -- 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
** Also affects: networking-odl Importance: Undecided Status: New ** Changed in: networking-odl Status: New => In Progress ** Changed in: networking-odl Assignee: (unassigned) => lei zhang (zhang-lei) -- 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: In Progress Status in cloudkitty: In Progress Status in Designate: In Progress Status in DragonFlow: 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 networking-odl: In Progress Status in networking-ofagent: 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 -- 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 1530742] Re: Change LOG.warn to LOG.warning
*** This bug is a duplicate of bug 1508442 *** https://bugs.launchpad.net/bugs/1508442 ** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => lei zhang (zhang-lei) -- 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/1530742 Title: Change LOG.warn to LOG.warning Status in Evoque: In Progress Status in Glance: New Status in Gnocchi: In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in keystoneauth: In Progress Status in Mistral: New Status in Murano: In Progress Status in oslo.messaging: In Progress Status in oslo.middleware: New Status in python-evoqueclient: In Progress Status in python-heatclient: In Progress Status in python-muranoclient: In Progress Status in senlin: Fix Released Status in tempest: In Progress Bug description: Python 3 deprecated the logger.warn method, see: https://docs.python.org/3/library/logging.html#logging.warning so we prefer to use warning to avoid DeprecationWarning. To manage notifications about this bug go to: https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning
*** This bug is a duplicate of bug 1508442 *** https://bugs.launchpad.net/bugs/1508442 ** No longer affects: glance -- 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/1530742 Title: Change LOG.warn to LOG.warning Status in ceilometer-powervm: Fix Released Status in CloudPulse: New Status in Evoque: Fix Released Status in Gnocchi: Fix Committed Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): In Progress Status in keystoneauth: In Progress Status in Kingbird: New Status in Mistral: New Status in Murano: Fix Released Status in openstack-ansible: New Status in oslo.messaging: In Progress Status in oslo.middleware: New Status in oslo.vmware: New Status in python-cloudpulseclient: New Status in python-evoqueclient: In Progress Status in python-heatclient: In Progress Status in python-muranoclient: Fix Released Status in senlin: Fix Released Status in Stackalytics: New Status in tacker: Fix Released Status in tempest: In Progress Bug description: Python 3 deprecated the logger.warn method, see: https://docs.python.org/3/library/logging.html#logging.warning so we prefer to use warning to avoid DeprecationWarning. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer-powervm/+bug/1530742/+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
** Also affects: octavia Importance: Undecided Status: New ** Changed in: octavia Assignee: (unassigned) => lei zhang (zhang-lei) -- 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 cloudkitty: In Progress Status in Designate: In Progress Status in Glance: In Progress Status in Gnocchi: In Progress Status in heat: In Progress Status in Ironic: Fix Released Status in Ironic Inspector: Fix Released Status in ironic-lib: Fix Committed Status in ironic-python-agent: Fix Committed Status in OpenStack Identity (keystone): In Progress Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: In Progress Status in neutron: In Progress Status in nova-powervm: Fix Released Status in octavia: New Status in Packstack: In Progress Status in python-magnumclient: In Progress Status in tempest: In Progress Status in tripleo: New Status in tuskar: In Progress Status in zaqar: In Progress Bug description: LOG.warn is deprecated. But it still used in a few places, non- deprecated LOG.warning should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+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 1489059] Re: "db type could not be determined" running py34
** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Status: New => In Progress ** Changed in: horizon Assignee: (unassigned) => lei zhang (zhang-lei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in cloudkitty: Fix Committed Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic: Fix Released Status in ironic-lib: In Progress Status in OpenStack Identity (keystone): Fix Committed Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Committed Status in Manila: Fix Released Status in networking-midonet: In Progress Status in networking-ofagent: New Status in neutron: Fix Released Status in python-glanceclient: In Progress Status in python-keystoneclient: Fix Committed Status in Sahara: Fix Released Status in senlin: Fix Committed Status in tap-as-a-service: New Status in tempest: In Progress Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1489059] Re: "db type could not be determined" running py34
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Status: New => In Progress ** Changed in: zaqar Assignee: (unassigned) => lei zhang (zhang-lei) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in cloudkitty: Fix Committed Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic: Fix Released Status in ironic-lib: In Progress Status in OpenStack Identity (keystone): Fix Committed Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Committed Status in Manila: Fix Released Status in networking-midonet: In Progress Status in networking-ofagent: New Status in neutron: Fix Released Status in python-glanceclient: In Progress Status in python-keystoneclient: Fix Committed Status in Sahara: Fix Released Status in senlin: Fix Committed Status in tap-as-a-service: New Status in tempest: In Progress Status in zaqar: In Progress Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Also affects: magnum Importance: Undecided Status: New ** Changed in: magnum Assignee: (unassigned) => lei zhang (zhang-lei) -- 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Barbican: In Progress Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in congress: In Progress Status in Designate: In Progress Status in Glance: Fix Committed Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Keystone: Fix Committed Status in Magnum: New Status in Manila: In Progress Status in Mistral: In Progress Status in murano: Fix Committed Status in OpenStack Compute (nova): Won't Fix Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in python-designateclient: In Progress Status in python-mistralclient: In Progress Status in Python client library for Zaqar: In Progress Status in Sahara: Fix Released Status in zaqar: In Progress Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1259292/+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 1490764] Re: Wrong handling of domain_id passed as None
domain_id is not a variable, it can't be None as in: https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L743 This step is just to judge whether ref['domain_id'] is already exists ** Changed in: keystone Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1490764 Title: Wrong handling of domain_id passed as None Status in Keystone: Invalid Bug description: Keystone does not handle the domain_id passed as none in controller layer, as in: https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L743 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1490764/+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
