[Yahoo-eng-team] [Bug 1536437] [NEW] 'module' object has no attribute 'moved_function' failure when buildnig debian package for Mitaka b2

[Thomas Goirand]

Public bug reported:

When building the Debian package of Neutron for the Mitaka b2 release, I
get the below unit test failures. All other tests are ok (6451 tests).
Please help me to fix these last 3.


==
FAIL: 
unittest2.loader._FailedTest.neutron.tests.unit.agent.linux.test_bridge_lib
unittest2.loader._FailedTest.neutron.tests.unit.agent.linux.test_bridge_lib
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
neutron.tests.unit.agent.linux.test_bridge_lib
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "neutron/tests/unit/agent/linux/test_bridge_lib.py", line 20, in 
from neutron.agent.linux import bridge_lib
  File "neutron/agent/linux/bridge_lib.py", line 23, in 
from neutron.i18n import _LE
  File "neutron/i18n.py", line 25, in 
_ = moves.moved_function(neutron._i18n._, '_', __name__, message=message)
AttributeError: 'module' object has no attribute 'moved_function'


==
FAIL: unittest2.loader._FailedTest.neutron.tests.unit.cmd.server
unittest2.loader._FailedTest.neutron.tests.unit.cmd.server
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: neutron.tests.unit.cmd.server
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 490, in 
_find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "neutron/tests/unit/cmd/server/__init__.py", line 16, in 
from neutron.cmd.eventlet import server
  File "neutron/cmd/eventlet/server/__init__.py", line 17, in 
from neutron.server import wsgi_pecan
  File "neutron/server/wsgi_pecan.py", line 23, in 
from neutron.pecan_wsgi import app as pecan_app 
  File "neutron/pecan_wsgi/app.py", line 23, in 
from neutron.pecan_wsgi import hooks
  File "neutron/pecan_wsgi/hooks/__init__.py", line 23, in 
from neutron.pecan_wsgi.hooks import translation
  File "neutron/pecan_wsgi/hooks/translation.py", line 22, in 
from neutron.i18n import _LE
  File "neutron/i18n.py", line 25, in 
_ = moves.moved_function(neutron._i18n._, '_', __name__, message=message)
AttributeError: 'module' object has no attribute 'moved_function'

==
FAIL: 
unittest2.loader._FailedTest.neutron.tests.unit.plugins.ml2.drivers.linuxbridge.agent.test_linuxbridge_neutron_agent
unittest2.loader._FailedTest.neutron.tests.unit.plugins.ml2.drivers.linuxbridge.agent.test_linuxbridge_neutron_agent
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
neutron.tests.unit.plugins.ml2.drivers.linuxbridge.agent.test_linuxbridge_neutron_agent
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"neutron/tests/unit/plugins/ml2/drivers/linuxbridge/agent/test_linuxbridge_neutron_agent.py",
 line 21, in 
from neutron.agent.linux import bridge_lib
  File "neutron/agent/linux/bridge_lib.py", line 23, in 
from neutron.i18n import _LE
  File "neutron/i18n.py", line 25, in 
_ = moves.moved_function(neutron._i18n._, '_', __name__, message=message)
AttributeError: 'module' object has no attribute 'moved_function'

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  'module' object has no attribute 'moved_function' failure when
  buildnig debian package for Mitaka b2

Status in neutron:
  New

Bug description:
  When building the Debian package of Neutron for the Mitaka b2 release,
  I get the below unit test failures. All other tests are ok (6451
  tests). Please help me to fix these last 3.

  
  ==
  FAIL: 
unittest2.loader._FailedTest.neutron.tests.unit.agent.linux.test_bridge_lib
  unittest2.loader._FailedTest.neutron.tests.unit.agent.linux.test_bridge_lib
  

[Yahoo-eng-team] [Bug 1536453] [NEW] swap volume failed because block copy still active

[jingtao liang]

Public bug reported:

version : kilo

description:

I migrate a volume which is in in-use status on lvm to another VG . It will be 
error in most time . I don‘t know why .
Becasuse when I don't use the volume on lvm to migrate .It will be ok.


product steps:

1 create a volume on VG
2 create a vm
3 attach the volume to the vm
4 migrate the volume to another VG.

error logs:

2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5582, in 
_swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] resize_to)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1232, in 
swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] self._swap_volume(virt_dom, disk_dev, 
conf.source_path, resize_to)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1203, in 
_swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] self._conn.defineXML(xml)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 183, in doit
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] result = proxy_call(self._autowrap, 
f, *args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 141, in proxy_call
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] rv = execute(f, *args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 122, in execute
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] six.reraise(c, e, tb)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 80, in tworker
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] rv = meth(*args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib64/python2.7/site-packages/libvirt.py", line 3632, in defineXML
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] if ret is None:raise 
libvirtError('virDomainDefineXML() failed', conn=self)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] libvirtError: block copy still active: 
domain has active block job
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] 
2016-01-21 11:13:41.686 27863 INFO nova.scheduler.client.report 
[req-c59264b3-9223-472e-b1c4-bfc3f5643393 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Compute_service record updated for 
('2C5_19_CG2', '2C5_19_CG2')
2016-01-21 11:13:41.687 27863 ERROR oslo_messaging.rpc.dispatcher 
[req-c59264b3-9223-472e-b1c4-bfc3f5643393 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Exception during message handling: 
block copy still active: domain has active block job
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher Traceback 
(most recent call last):
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, 
in _dispatch_and_reply
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, 
in _dispatch
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, 
in _do_dispatch
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 8262, 

[Yahoo-eng-team] [Bug 1535367] Re: Failure on SR-IOV . Missing 'parent_addr

[OpenStack Infra]

Reviewed:  https://review.openstack.org/269191
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=abcb26c121c7643201079121ca98266079edb8b8
Submitter: Jenkins
Branch:master

commit abcb26c121c7643201079121ca98266079edb8b8
Author: Nikola Dipanov 
Date:   Tue Jan 19 13:49:47 2016 +

Make sure that we always have a parent_addr set

Since enabling PF tracking in the following commit:

50355c4595e08f293f610da32247e405b20c1c5b

we expect all of the PciDevice objects to have a parent_addr field
set since we use it for matching in case the (miss-)feature of allowing
to specify a PF address to enable all VFs was used in the whitelist.

This caused a lazy-load on the object which always fails, so this patch
makes sure that 'parent_addr' field is set to None on the object even if
it was not passed in by the driver.

Closes-bug: #1535367
Change-Id: I0ed8dd0702287859f7809a1a1a87dafe168d6e9b


** Changed in: nova
   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/1535367

Title:
  Failure on SR-IOV .  Missing  'parent_addr

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Mellanox CI fails on SR-IOV hardware
  1.  Running nova from master commit ffa07781ab47baf096854cd6c22a3e433eab3f0d
  2. Full  logs http://144.76.193.39/ci-artifacts/269109/1/Nova-ML2-Sriov/
  3. Reproduce:
   ./stack.sh
   neutron port-create --binding:vnic_type=direct private
   nova boot --flavor m1.small --image mellanox_eth --nic port-id= 
vm1
  4.  port binding fails
   nova fails to find appropriate host

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1535367/+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 1536253] Re: nova floating-ip-list - ERROR (ClientException): Unexpected API Error

[Augustina Ragwitz]

*** This bug is a duplicate of bug 1526721 ***
https://bugs.launchpad.net/bugs/1526721

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

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1526721
   After add networking service using  provider networks , access the dashboard 
will throw a error "Unable to retrieve floating IP addresses".

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

Title:
  nova floating-ip-list - ERROR (ClientException): Unexpected API Error

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Compute (nova):
  New
Status in openstack-manuals:
  New

Bug description:
  I've installed libverty openstack release on Ubuntu 14.04 with flat network. 
  The openstack release is 12.0.0. 

  dpkg -l | grep nova-common
  ii  nova-common   2:12.0.0-0ubuntu2~cloud0
all  OpenStack Compute - common files

  Everything seems to work fine, except horizon. 
  When I logged in , getting an error message "Error: Unable to retrieve 
floating IP addresses."
  Provisioning of VMs is not working in horizon, failed with error. But nova 
boot is working fine and instance is up and running. 
  Also when I try to run the commands :
nova floating-ip-list
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) 
(Request-ID: req-c088103b-c871-480f-8741-cbb4e9139d05)
   neutron floatingip-list 
  404 Not Found
  The resource could not be found.

  The nova-api.log file is looking as below :
  2016-01-20 18:00:46.764 18894 INFO nova.osapi_compute.wsgi.server 
[req-310e6d1a-1a47-43cb-8a86-5a15ceaa9225 9840f0220bfa4542b2edb02958b84f53 
55570ea7c23544f5b572f708390b0471 - - -] 9.148.27.248 "GET /v2/ HTTP/1.1" 
status: 200 len: 572 time: 0.5391979
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
[req-dda981f3-947a-4d05-93fb-180ae2b96d9f 9840f0220bfa4542b2edb02958b84f53 
55570ea7c23544f5b572f708390b0471 - - -] Unexpected exception in API method
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/floating_ips.py", 
line 122, in index
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
floating_ips = self.network_api.get_floating_ips_by_project(context)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 1402, in 
get_floating_ips_by_project
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions fips = 
client.list_floatingips(tenant_id=project_id)['floatingips']
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 102, in 
with_params
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions ret = 
self.function(instance, *args, **kwargs)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 731, in 
list_floatingips
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
**_params)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 307, in 
list
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions for r 
in self._pagination(collection, path, **params):
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 320, in 
_pagination
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions res = 
self.get(path, params=params)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 293, in 
get
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
headers=headers, params=params)
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 270, in 
retry_request
  2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
headers=headers, params=params)
  2016-01-20 18:00:47.098 

[Yahoo-eng-team] [Bug 1536442] Re: swap volume is not available because the parameters are opposite

[Sean McGinnis]

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

** No longer affects: cinder

** Tags added: volumes

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

Title:
  swap volume is not available because the parameters are opposite

Status in OpenStack Compute (nova):
  New

Bug description:
  version: kilo

  description:

  in the file：/nova/compute/manager.py   . the functions like this:

  class _ComputeV4Proxy(object):
  
  def swap_volume(self, ctxt, instance, old_volume_id, new_volume_id):
  return self.manager.swap_volume(ctxt, instance, old_volume_id,
  new_volume_id)

  
  class ComputeManager(manager.Manager):
  
 @wrap_exception()
  @reverts_task_state
  @wrap_instance_fault
  def swap_volume(self, context, old_volume_id, new_volume_id, instance):

  
  you see ,the parameters of instance should be in the right place .

  
  product steps:

  1 create a volume
  2 create a vm
  3 attach the volume to the vm
  4 migrate the volume to another backend.

  
  error logs:

  2016-01-21 10:57:24.916 24271 ERROR root 
[req-15d4d656-06ee-4c02-8da0-af779944 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Original exception being dropped: 
['Traceback (most recent call last):\n', '  File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 392, in 
decorated_function\nreturn function(self, context, *args, **kwargs)\n', '  
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5628, in 
swap_volume\ninstance.uuid)\n', "AttributeError: 'unicode' object has no 
attribute 'uuid'\n"]
  2016-01-21 10:57:24.916 24271 ERROR root 
[req-15d4d656-06ee-4c02-8da0-af779944 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Original exception being dropped: 
['Traceback (most recent call last):\n', '  File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 347, in 
decorated_function\nreturn function(self, context, *args, **kwargs)\n', '  
File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 404, in 
decorated_function\nkwargs[\'instance\'], e, sys.exc_info())\n', '  File 
"/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 89, in 
add_instance_fault_from_exc\nfault_obj.instance_uuid = instance.uuid\n', 
"AttributeError: 'unicode' object has no attribute 'uuid'\n"]
  2016-01-21 10:57:24.917 24271 ERROR oslo_messaging.rpc.dispatcher 
[req-15d4d656-06ee-4c02-8da0-af779944 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Exception during message handling: 
string indices must be integers
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher Traceback 
(most recent call last):
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, 
in _dispatch_and_reply
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, 
in _dispatch
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, 
in _do_dispatch
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher result 
= func(ctxt, **new_args)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 8262, in 
swap_volume
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher 
new_volume_id)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/exception.py", line 88, in wrapped
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 85, in __exit__
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/exception.py", line 71, in wrapped
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 363, in 
decorated_function
  2016-01-21 10:57:24.917 24271 TRACE oslo_messaging.rpc.dispatcher 

[Yahoo-eng-team] [Bug 1536471] [NEW] (HTTP 500)

[BM Shukla]

Public bug reported:

I was trying to launch 4 instances and I got the following bug related
error.

Error: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: req-
b040cba1-3d89-46fd-bf84-7af8340bc6ec)

Error: Unable to launch 4 instances named "b1",
===Log /var/log/nova/nova-api.log==
2016-01-21 10:42:00.985 2234 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.24 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004308
2016-01-21 10:42:02.084 2235 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.23 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004361
2016-01-21 10:42:02.986 2236 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.24 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004480
2016-01-21 10:42:04.085 2236 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.23 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004470
2016-01-21 10:42:04.700 2240 INFO nova.osapi_compute.wsgi.server 
[req-f05658ec-b990-4fd7-9a32-7761ec904456 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/se
rvers/22976120-860d-49bd-aa28-4554f24ebe72 HTTP/1.1" status: 200 len: 1480 
time: 0.0602472
2016-01-21 10:42:04.716 2240 INFO nova.osapi_compute.wsgi.server 
[req-549c5390-4568-4e24-a2b5-dc56e6f88bc2 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/fl
avors/1 HTTP/1.1" status: 200 len: 610 time: 0.0127289
2016-01-21 10:42:04.879 2234 INFO nova.osapi_compute.wsgi.server 
[req-740b5f61-b4a8-452a-9629-c6013b2886e7 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/ex
tensions HTTP/1.1" status: 200 len: 21875 time: 0.0231891
2016-01-21 10:42:04.987 2235 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.24 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004358
2016-01-21 10:42:06.087 2235 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.23 
"OPTIONS / HTTP/1.0" status: 200 len: 495 t
ime: 0.0004370

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
   (HTTP 500)

Status in OpenStack Compute (nova):
  New

Bug description:
  I was trying to launch 4 instances and I got the following bug related
  error.

  Error: Unexpected API Error. Please report this at
  http://bugs.launchpad.net/nova/ and attach the Nova API log if
  possible.  (HTTP 500) (Request-
  ID: req-b040cba1-3d89-46fd-bf84-7af8340bc6ec)

  Error: Unable to launch 4 instances named "b1",
  ===Log /var/log/nova/nova-api.log==
  2016-01-21 10:42:00.985 2234 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.24 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004308
  2016-01-21 10:42:02.084 2235 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.23 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004361
  2016-01-21 10:42:02.986 2236 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.24 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004480
  2016-01-21 10:42:04.085 2236 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.23 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004470
  2016-01-21 10:42:04.700 2240 INFO nova.osapi_compute.wsgi.server 
[req-f05658ec-b990-4fd7-9a32-7761ec904456 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/se
  rvers/22976120-860d-49bd-aa28-4554f24ebe72 HTTP/1.1" status: 200 len: 1480 
time: 0.0602472
  2016-01-21 10:42:04.716 2240 INFO nova.osapi_compute.wsgi.server 
[req-549c5390-4568-4e24-a2b5-dc56e6f88bc2 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/fl
  avors/1 HTTP/1.1" status: 200 len: 610 time: 0.0127289
  2016-01-21 10:42:04.879 2234 INFO nova.osapi_compute.wsgi.server 
[req-740b5f61-b4a8-452a-9629-c6013b2886e7 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/ex
  tensions HTTP/1.1" status: 200 len: 21875 time: 0.0231891
  2016-01-21 10:42:04.987 2235 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.24 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004358
  2016-01-21 10:42:06.087 2235 INFO nova.osapi_compute.wsgi.server [-] 
10.0.0.23 "OPTIONS / HTTP/1.0" status: 200 len: 495 t
  ime: 0.0004370

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

[Yahoo-eng-team] [Bug 1471685] Re: Entering illegal values or empty values in network fields does not generate an error message

[Masco]

since we can have a gateway ip from out of the subnet range, marking
this bug as invalid.

** Changed in: horizon
   Status: In Progress => Invalid

** Changed in: horizon
 Assignee: Masco (masco) => (unassigned)

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

Title:
   Entering illegal values or empty values in network fields does not
  generate an error message

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Description of problem:
  When trying to create a new network with illegal values or empty values in 
its fields, error message is not generated indicating the incorrect fields  
 

  Version-Release number of selected component (if applicable):
  python-django-horizon-2015.1.0-10.el7ost.noarch

  How reproducible:
  100%

  Steps to Reproduce:
  1. Create a network with illegal values or empty values   

  
  Actual results:
  Nothing happens 

  Expected results:
  Error message should be appeared and the incorrect fields should be 
highlighted in red

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1471685/+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 1536441] [NEW] Project can not be fully displayed

[space]

Public bug reported:

  Project can not be fully displayed at the top-left corner if there are
too many projects.I think it should change column to display if the
first column is full.

** Affects: horizon
 Importance: Undecided
 Assignee: space (fengzhr)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => space (fengzhr)

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

Title:
  Project can not be fully displayed

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
Project can not be fully displayed at the top-left corner if there
  are too many projects.I think it should change column to display if
  the first column is full.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536441/+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 1527417] Re: Horizon eslintrc uses deprecated rule names

[OpenStack Infra]

Reviewed:  https://review.openstack.org/259234
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=846413c14913d3afd6f5d73d261c6ccae65adfb0
Submitter: Jenkins
Branch:master

commit 846413c14913d3afd6f5d73d261c6ccae65adfb0
Author: Rajat Vig 
Date:   Thu Dec 17 16:31:15 2015 -0800

Update eslint-plugin-angular to the latest

eslint-plugin-angular in use by the project is
quite old and the new library has changed rules.
This patch updates the library and fixes the code
where rule names have changed.

Change-Id: I2e60a07b899325f17f38b96d40325602b4b58219
Closes-Bug: #1527417


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  Horizon eslintrc uses deprecated rule names

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  angular/ng_controller_as_vm is deprecated in favor of angular/controller-as-vm
  angular/ng_no_cookiestore is deprecated in favor of  angular/no-cookiestore

  Horizon should use the new rule names

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1527417/+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 1536470] [NEW] Fixing test cases

[sanjana]

Public bug reported:

The tests in ceilometer_tests.py file for fetching the meter list,
sample list and the resource list are incomplete. It verifies the API
call, but the API could fail completely and an empty list would pass the
assertion.

** Affects: horizon
 Importance: Undecided
 Assignee: sanjana (sanjana)
 Status: New

** Description changed:

- The tests in ceilometer.py file for fetching the meter list, sample list
- and the resource list are incomplete. It verifies the API call, but the
- API could fail completely and an empty list would pass the assertion.
+ The tests in ceilometer_tests.py file for fetching the meter list,
+ sample list and the resource list are incomplete. It verifies the API
+ call, but the API could fail completely and an empty list would pass the
+ assertion.

** Changed in: horizon
 Assignee: (unassigned) => sanjana (sanjana)

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

Title:
  Fixing test cases

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The tests in ceilometer_tests.py file for fetching the meter list,
  sample list and the resource list are incomplete. It verifies the API
  call, but the API could fail completely and an empty list would pass
  the assertion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536470/+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 1510826] Re: Move midonet interface driver from neutron to networking-midonet repo

[YAMAMOTO Takashi]

** Changed in: networking-midonet
   Status: Fix Committed => Fix Released

** Changed in: networking-midonet
   Importance: Undecided => Low

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

Title:
  Move midonet interface driver from neutron to networking-midonet repo

Status in networking-midonet:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  this bug tracks the status of moving midonet interface driver from
  neutron to networking-midonet repo

  http://docs.openstack.org/developer/neutron/devref/contribute.html
  #interface-drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1510826/+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 1268439] Re: range method is not same in py3.x and py2.x

[MD NADEEM]

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

** Changed in: kolla
 Assignee: (unassigned) => MD NADEEM (mail2nadeem92)

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

Title:
  range method is not same in py3.x and py2.x

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Identity (keystone):
  Invalid
Status in kolla:
  In Progress
Status in neutron:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-neutronclient:
  Invalid
Status in python-swiftclient:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress

Bug description:
  in py3.x,range is xrange in py2.x.
  in py3.x, if you want get a list,you must use:
  list(range(value))

  I review the code, find that many codes use range for  loop, if used py3.x 
environment,
  it will occure error.
  so we must modify this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1268439/+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 1535725] Re: tox command doesn't work anymore to run neutron tests

[OpenStack Infra]

Reviewed:  https://review.openstack.org/269633
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=3b2b277979f8d0335fcfcef29893290ef20cb9f7
Submitter: Jenkins
Branch:master

commit 3b2b277979f8d0335fcfcef29893290ef20cb9f7
Author: Mathieu Rohon 
Date:   Tue Jan 19 13:28:24 2016 +

bump the min tox version to 2.3.1

When tox 2.3.0 uses the tox.ini provided by neutron,
the following bug is hitten :
https://bitbucket.org/hpk42/tox/issues/181
We need to set the min version of tox to 2.3.1.

Change-Id: If2c3f4f534ff23a1f649cebea15e945563173544
Closes-bug: #1535725


** 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 neutron.
https://bugs.launchpad.net/bugs/1535725

Title:
  tox command doesn't work anymore to run neutron tests

Status in neutron:
  Fix Released

Bug description:
  using tox 2.3.0 with the tox.ini from neutron leads to this kind of
  error:

  $ tox -e pep8
  Traceback (most recent call last):
File "/usr/local/bin/tox", line 11, in 
  sys.exit(cmdline())
File "/usr/local/lib/python2.7/dist-packages/tox/session.py", line 38, in 
main
  config = prepare(args)
File "/usr/local/lib/python2.7/dist-packages/tox/session.py", line 26, in 
prepare
  config = parseconfig(args)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 229, in 
parseconfig
  parseini(config, inipath)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 729, in 
__init__
  self.make_envconfig(name, section, reader._subs, config)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 760, in 
make_envconfig
  res = meth(env_attr.name, env_attr.default)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 893, in 
getdict_setenv
  definitions = self._getdict(value, default=default, sep=sep)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 904, in 
_getdict
  name, rest = line.split('=', 1)
  ValueError: need more than 1 value to unpack

  The root cause seems to be a bug in tox 2.3.0 : 
  https://bitbucket.org/hpk42/tox/issues/181

  It works fine with tox 2.3.1.

  Other openstack projects report similar errors :

  https://bugs.launchpad.net/devstack/+bug/1525352

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1535725/+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 1535707] Re: Create router with external network attached doesn't create router namespace

[Akihiro Motoki]

It is found in Horizon, but it is actually a neutron bug.

I created a router with external_gateway_info, but the router created did not 
appear on a network node.
The detail step on a single node with devstack is found at: 
http://paste.openstack.org/show/484507/


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

** Changed in: horizon
   Importance: Undecided => High

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
   Status: New => Confirmed

** Tags added: l3-ipam-dhcp neutron

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

Title:
  Create router with external network attached doesn't create router
  namespace

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in neutron:
  Confirmed

Bug description:
  Description of problem:
  In Horizon when creating a router with an external network attached from the 
Create Router form a router namespace doesn't get created on the controller.

  Steps to Reproduce:
  1. Go to Project-> Network -> Routers
  2. Click Create Router
  3. Input name, Admin state UP and select an External Network from the list 

  Actual results:
  Router gets created but no router namespace gets created on the controller. 

  Expected results:
  Router namespace gets created on the controller with an IP assigned from the 
selected external network.

  Additional info:
  If I don't select the external network in the Create Router form when I 
create it and attach it to the external network afterwards by using the set 
gateway button then the router namespace gets created ok.

  to check the router namespace list, run this below command in the controller 
node.
  "sudo ip netns list"

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535707/+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 1536501] [NEW] type 'exceptions.ValueError'> (HTTP 500)

[BM Shukla]

Public bug reported:

Error: Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: req-
bbc92040-0851-4ed3-aa6b-b9dbee31937e)

Nova API  Log==
2016-01-21 12:47:36.713 2240 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.24 
"OPTIONS / HTTP/1.0" status: 200 len: 495 time: 0.0003982
2016-01-21 12:47:37.682 2240 INFO nova.osapi_compute.wsgi.server 
[req-0127a895-ddd0-4830-ac16-3b95d54d0da4 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/os-availability-zone HTTP/1.1" status: 200 
len: 288 time: 0.0212719
2016-01-21 12:47:37.697 2240 INFO nova.osapi_compute.wsgi.server 
[req-1cf91ceb-1d8b-4855-97e4-fe2aaf6e4636 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/flavors/detail HTTP/1.1" status: 200 len: 
2262 time: 0.0129042
2016-01-21 12:47:37.855 2235 INFO nova.osapi_compute.wsgi.server 
[req-cb6c2139-55c5-41e9-b211-4254f231ce82 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/os-quota-sets/ec098278ee4145a3be4cf528e7ca41e9
 HTTP/1.1" status: 200 len: 563 time: 0.0082810
2016-01-21 12:47:38.156 2236 INFO nova.osapi_compute.wsgi.server 
[req-c0964f0d-5b79-415b-8ccc-49ec1d37fe0f 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/servers/detail?project_id=ec098278ee4145a3be4cf528e7ca41e9_id=ec098278ee4145a3be4cf528e7ca41e9
 HTTP/1.1" status: 200 len: 12359 time: 0.2918830
2016-01-21 12:47:38.434 2234 INFO nova.osapi_compute.wsgi.server 
[req-eefdfa88-6ab4-46ab-811a-cdf11b8ecfdb 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/os-keypairs HTTP/1.1" status: 200 len: 721 
time: 0.0051420
2016-01-21 12:47:38.552 2234 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.23 
"OPTIONS / HTTP/1.0" status: 200 len: 495 time: 0.0004861
2016-01-21 12:47:38.583 2240 INFO nova.osapi_compute.wsgi.server 
[req-12be44b8-4f53-467e-b884-c277278eb302 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] 10.0.0.13,10.0.0.24 "GET 
/v2/ec098278ee4145a3be4cf528e7ca41e9/extensions HTTP/1.1" status: 200 len: 
21875 time: 0.0242469
2016-01-21 12:47:38.714 2235 INFO nova.osapi_compute.wsgi.server [-] 10.0.0.24 
"OPTIONS / HTTP/1.0" status: 200 len: 495 time: 0.0004449
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions 
[req-bbc92040-0851-4ed3-aa6b-b9dbee31937e 00dc39936ac247c8a47d4c38845b7a28 
ec098278ee4145a3be4cf528e7ca41e9 - - -] Unexpected exception in API method
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 73, in 
wrapper
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 
611, in create
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions 
**create_kwargs)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/hooks.py", line 149, in inner
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions rv = 
f(*args, **kwargs)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1581, in create
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions 
check_server_group_quota=check_server_group_quota)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1181, in 
_create_instance
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions 
auto_disk_config, reservation_id, max_count)
2016-01-21 12:47:38.990 2240 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 940, in 
_validate_and_build_base_options
2016-01-21 12:47:38.990 2240 ERROR 

[Yahoo-eng-team] [Bug 1536509] [NEW] boot n-cpu from a clean database lead to pci passthrough stop work

[Yongli He]

Public bug reported:

first time boot nova or clean the pci devices from nova database then
reboot n-cpu, will leading to scheduling the VM with pci devices fail.
if then reboot the n-cpu, everything is ok.

i suspect this related to recently pci stats changes, but not confirm
yet.  this bug now block the third-party pci-test.

** Affects: nova
 Importance: Undecided
 Status: New

** Description changed:

- first time boot nova or clean the pci devices from nova database will
- leading to scheduling the VM with pci devices fail.   then reboot the
- n-cpu, everything is ok.
+ first time boot nova or clean the pci devices from nova database then
+ reboot n-cpu, will leading to scheduling the VM with pci devices fail.
+ if then reboot the n-cpu, everything is ok.
  
  i suspect this related to recently pci stats changes, but not confirm
  yet.  this bug now block the third-party pci-test.

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

Title:
  boot n-cpu from a clean database lead to pci passthrough stop work

Status in OpenStack Compute (nova):
  New

Bug description:
  first time boot nova or clean the pci devices from nova database then
  reboot n-cpu, will leading to scheduling the VM with pci devices fail.
  if then reboot the n-cpu, everything is ok.

  i suspect this related to recently pci stats changes, but not confirm
  yet.  this bug now block the third-party pci-test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536509/+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 1536214] [NEW] PO files broken

[Andreas Jaeger]

Public bug reported:

python setup.py compile_catalog fails to compile the existing translated
files for Spanish and Turkish - both in master and liberty.

Suggested action:
1) Fix the strings in translation server so that next translation import gets 
strings that are valid
2) Add lint check that checks that translations are valid.

For 2: Add to tox.ini a check like it's done for keystone:
  # Check that .po and .pot files are valid.
  bash -c "find nova -type f -regex '.*\.pot?' -print0| \
   xargs -0 -n 1 msgfmt --check-format -o /dev/null"

Change 2)  will take care that the daily translation import cannot
import again non-valid translations. 2) should only merge once 1) is
fixed and imported.

** Affects: nova
 Importance: High
 Assignee: Andreas Jaeger (jaegerandi)
 Status: In Progress

** Affects: nova/kilo
 Importance: Undecided
 Status: New

** Affects: nova/liberty
 Importance: High
 Assignee: Andreas Jaeger (jaegerandi)
 Status: In Progress


** Tags: i18n

** Changed in: nova
 Assignee: (unassigned) => Andreas Jaeger (jaegerandi)

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

Title:
  PO files broken

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) kilo series:
  New
Status in OpenStack Compute (nova) liberty series:
  In Progress

Bug description:
  python setup.py compile_catalog fails to compile the existing
  translated files for Spanish and Turkish - both in master and liberty.

  Suggested action:
  1) Fix the strings in translation server so that next translation import gets 
strings that are valid
  2) Add lint check that checks that translations are valid.

  For 2: Add to tox.ini a check like it's done for keystone:
# Check that .po and .pot files are valid.
bash -c "find nova -type f -regex '.*\.pot?' -print0| \
 xargs -0 -n 1 msgfmt --check-format -o /dev/null"

  Change 2)  will take care that the daily translation import cannot
  import again non-valid translations. 2) should only merge once 1) is
  fixed and imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536214/+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 1536226] [NEW] Not all pot files compiled

[Andreas Jaeger]

Public bug reported:

python setup.py compile_catalog only compiles the main nova.pot files to
nova.mo, there're no instructions on how to compile the log level files.

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: openstack-i18n
 Importance: Undecided
 Status: New

** Also affects: openstack-i18n
   Importance: Undecided
   Status: New

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

Title:
  Not all pot files compiled

Status in OpenStack Compute (nova):
  New
Status in openstack i18n:
  New

Bug description:
  python setup.py compile_catalog only compiles the main nova.pot files
  to nova.mo, there're no instructions on how to compile the log level
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536226/+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 1536087] Re: Themes directory should be ignored

[Rob Cresswell]

** Changed in: horizon
   Status: In Progress => Invalid

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

Title:
  Themes directory should be ignored

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Alternate themes are useful for testing and other customisations.
  Rather than using global git excludes or other workarounds, Horizon
  could just exclude the themes directory except for the "default" theme
  and the alternate "material" example theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536087/+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 1526710] Re: NotSupportedError: MySQL cannot rename indexes

[Federico Ressi]

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

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

Title:
  NotSupportedError: MySQL cannot rename indexes

Status in Glance:
  Invalid

Bug description:
  When stacking with branch stable/liberty of devstack, on a control host I had 
below error.
  I am using a clean Ubuntu 14.04 LTS just updated.

  
  2015-12-16 07:50:32.262 | 2015-12-16 07:50:32.262 INFO migrate.versioning.api 
[-] 0 -> 1... 
  2015-12-16 07:50:32.272 | 2015-12-16 07:50:32.272 INFO 
glance.db.sqlalchemy.migrate_repo.schema [-] creating table images
  2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api 
[-] done
  2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api 
[-] 1 -> 2... 
  2015-12-16 07:50:32.303 | 2015-12-16 07:50:32.303 INFO 
glance.db.sqlalchemy.migrate_repo.schema [-] creating table image_properties
  2015-12-16 07:50:32.350 | 2015-12-16 07:50:32.350 INFO migrate.versioning.api 
[-] done
  2015-12-16 07:50:32.351 | 2015-12-16 07:50:32.351 INFO migrate.versioning.api 
[-] 2 -> 3... 
  2015-12-16 07:50:32.374 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api 
[-] done
  2015-12-16 07:50:32.376 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api 
[-] 3 -> 4... 
  2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api 
[-] done
  2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api 
[-] 4 -> 5... 
  2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.398 INFO migrate.versioning.api 
[-] done
  2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.399 INFO migrate.versioning.api 
[-] 5 -> 6... 
  2015-12-16 07:50:32.404 | 2015-12-16 07:50:32.404 CRITICAL glance [-] 
NotSupportedError: MySQL cannot rename indexes
  2015-12-16 07:50:32.406 | 
  2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance Traceback 
(most recent call last):
  2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/bin/glance-manage", line 10, in 
  2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance 
sys.exit(main())
  2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/opt/stack/glance/glance/cmd/manage.py", line 314, in main
  2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance return 
CONF.command.action_fn()
  2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/opt/stack/glance/glance/cmd/manage.py", line 170, in sync
  2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance 
CONF.command.current_version)
  2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/opt/stack/glance/glance/cmd/manage.py", line 115, in sync
  2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance version)
  2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line 
79, in db_sync
  2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance migration 
= versioning_api.upgrade(engine, repository, version)
  2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, 
in upgrade
  2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance return 
_migrate(url, repository, version, upgrade=True, err=err, **opts)
  2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance   File 
"", line 2, in _migrate
  2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", 
line 160, in with_engine
  2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance return 
f(*a, **kw)
  2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 366, 
in _migrate
  2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance 
schema.runchange(ver, change, changeset.step)
  2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 93, 
in runchange
  2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance 
change.run(self.engine, step)
  2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line 
148, in run
  2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance 
script_func(engine)
  2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/006_key_to_name.py",
 line 96, in upgrade
  2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance 
index.rename('ix_image_properties_image_id_name')
  2015-12-16 07:50:32.413 | 

[Yahoo-eng-team] [Bug 1536300] [NEW] Catalog response is inconsistent for domain scoped token

[Haneef Ali]

Public bug reported:

Some of the endpoints include tenant information and if we use domain
scoped token there is no tenant information.  So the catalog doesn't
have any entry for those services for domain scoped token which looks
odd

Since domain scoped token is used only by identity, the better apprach
would be to include  just identity catalog for domain scoped token.

e.g

Given below is the current response for domain scoped token.  What is
heat service's endpoint from this response?

| heat   | orchestration |  |
| nova   | compute   |  |
| cinder | volume|  |
||   |   internal: http://10.240.20.2:9090  |
||   | region1  |
||   |   public: https://myhelion.test:9090 |
||   | region1  |
||   |   admin: http://10.240.20.2:9090 |
| ceilometer | metering  | region1  |
||   |   internal: http://10.240.20.2:8777/ |
||   | region1  |
||   |   admin: http://10.240.20.2:8777/|
||   | region1  |
||   |   public: https://myhelion.test:8777/|
||   |  |
| glance | image | region1  |
||   |   public: https://myhelion.test:9292 |
||   | region1  |
||   |   internal: http://10.240.20.2:9292  |
||   | region1  |
||   |   admin: http://10.240.20.2:9292 |
||   |  |

** Affects: keystone
 Importance: Undecided
 Status: New

** Description changed:

  Some of the endpoints include tenant information and if we use domain
  scoped token there is no tenant information.  So the catalog doesn't
  have any entry for those services for domain scoped token which looks
  odd
  
- 
- Since domain scoped token is used only by identity, the better apprach would 
be to include  just identity catalog for domain scoped token.
+ Since domain scoped token is used only by identity, the better apprach
+ would be to include  just identity catalog for domain scoped token.
  
  e.g
  
  Given below is the current response for domain scoped token.  What is
  heat service's endpoint from this response?
  
  | heat   | orchestration |  |
  | nova   | compute   |  |
  | cinder | volume|  |
  ||   |   internal: http://10.240.20.2:9090  |
  ||   | region1  |
  ||   |   public: https://myhelion.test:9090 |
  ||   | region1  |
  ||   |   admin: http://10.240.20.2:9090 |
  | ceilometer | metering  | region1  |
  ||   |   internal: http://10.240.20.2:8777/ |
  ||   | region1  |
  ||   |   admin: http://10.240.20.2:8777/|
  ||   | region1  |
  ||   |   public: https://myhelion.test:8777/|
  ||   |  |
  | glance | image | region1  |
  ||   |   public: https://myhelion.test:9292 |
  ||   | region1  |
  ||   |   internal: http://10.240.20.2:9292  |
  ||   | region1  |
  ||   |   admin: http://10.240.20.2:9292 |
  ||   |  |

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

Title:
  Catalog response is inconsistent for domain scoped token

Status in OpenStack Identity 

[Yahoo-eng-team] [Bug 1536214] Re: PO files broken

[Matt Riedemann]

** Also affects: nova/kilo
   Importance: Undecided
   Status: New

** Also affects: nova/liberty
   Importance: Undecided
   Status: New

** Changed in: nova/liberty
 Assignee: (unassigned) => Andreas Jaeger (jaegerandi)

** Changed in: nova
   Status: New => In Progress

** Changed in: nova/liberty
   Status: New => In Progress

** Changed in: nova
   Importance: Undecided => High

** Changed in: nova/liberty
   Importance: Undecided => High

** Tags added: i18n

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

Title:
  PO files broken

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) kilo series:
  New
Status in OpenStack Compute (nova) liberty series:
  In Progress

Bug description:
  python setup.py compile_catalog fails to compile the existing
  translated files for Spanish and Turkish - both in master and liberty.

  Suggested action:
  1) Fix the strings in translation server so that next translation import gets 
strings that are valid
  2) Add lint check that checks that translations are valid.

  For 2: Add to tox.ini a check like it's done for keystone:
# Check that .po and .pot files are valid.
bash -c "find nova -type f -regex '.*\.pot?' -print0| \
 xargs -0 -n 1 msgfmt --check-format -o /dev/null"

  Change 2)  will take care that the daily translation import cannot
  import again non-valid translations. 2) should only merge once 1) is
  fixed and imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536214/+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 1318721] Re: RPC timeout in all neutron agents

[Corey Bryant]

Hui,

Thanks for the patches.  Your juno update to oslo.messaging is now being
regression tested in the trusty juno-staging PPA.  After testing passes
we'll promote it to cloud-archive:juno-proposed, and at that point we'll
also be able to upload the icehouse updates to trusty.

Regards,
Corey

** Changed in: neutron (Ubuntu)
   Status: New => In Progress

** Also affects: oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: neutron (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: oslo.messaging (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: oslo.messaging (Ubuntu)
   Status: New => Invalid

** Changed in: neutron (Ubuntu)
   Status: In Progress => Invalid

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/icehouse
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/juno
   Importance: Undecided
   Status: New

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: cloud-archive/juno
   Status: New => In Progress

** Changed in: cloud-archive/icehouse
   Status: New => In Progress

** Changed in: cloud-archive/icehouse
 Assignee: (unassigned) => Xiang Hui (xianghui)

** Changed in: cloud-archive/juno
 Assignee: (unassigned) => Xiang Hui (xianghui)

** Changed in: neutron (Ubuntu Trusty)
 Assignee: (unassigned) => Xiang Hui (xianghui)

** Changed in: oslo.messaging (Ubuntu Trusty)
 Assignee: (unassigned) => Xiang Hui (xianghui)

** Changed in: cloud-archive/juno
   Importance: Undecided => High

** Changed in: cloud-archive/icehouse
   Importance: Undecided => High

** Changed in: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: neutron (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
  RPC timeout in all neutron agents

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive icehouse series:
  In Progress
Status in Ubuntu Cloud Archive juno series:
  In Progress
Status in neutron:
  Invalid
Status in oslo.messaging:
  Fix Released
Status in neutron package in Ubuntu:
  Invalid
Status in oslo.messaging package in Ubuntu:
  Invalid
Status in neutron source package in Trusty:
  In Progress
Status in oslo.messaging source package in Trusty:
  In Progress

Bug description:
  In the logs the first traceback that happen is this:

  [-] Unexpected exception occurred 1 time(s)... retrying.
  Traceback (most recent call last):
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/excutils.py",
 line 62, in inner_func
  return infunc(*args, **kwargs)
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 741, in _consumer_thread

    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 732, in consume
  @excutils.forever_retry_uncaught_exceptions
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 660, in iterconsume
  try:
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 590, in ensure
  def close(self):
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 531, in reconnect
  # to return an error not covered by its transport
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 513, in _connect
  Will retry up to self.max_retries number of times.
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/neutron/openstack/common/rpc/impl_kombu.py",
 line 150, in reconnect
  use the callback passed during __init__()
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", 
line 508, in declare
  self.queue_bind(nowait)
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", 
line 541, in queue_bind
  self.binding_arguments, nowait=nowait)
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/kombu/entity.py", 
line 551, in bind_to
  nowait=nowait)
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/channel.py", 
line 1003, in queue_bind
  (50, 21),  # Channel.queue_bind_ok
    File 
"/opt/cloudbau/neutron-virtualenv/lib/python2.7/site-packages/amqp/abstract_channel.py",
 line 68, in wait
  return 

[Yahoo-eng-team] [Bug 1277104] Re: wrong order of assertEquals args

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264029
Committed: 
https://git.openstack.org/cgit/openstack/python-solumclient/commit/?id=6559731fb33bddccb364ab8430f6b41b1447f76f
Submitter: Jenkins
Branch:master

commit 6559731fb33bddccb364ab8430f6b41b1447f76f
Author: reedip 
Date:   Wed Jan 6 14:38:55 2016 +0900

Fix argument order for assertEqual to (expected, observed)

assertEqual expects that the arguments provided to it should be (expected, 
observed).
If a particluar order is kept as a convention, then it helps to provide a 
cleaner
message to the developer if Unit Tests fail.
The following patch fixes this issue

TrivialFix

Change-Id: I164dd6b2b820e4ca26bf3406f591ca786893f279
Closes-Bug: #1259292
Closes-Bug: #1277104


** Changed in: python-solumclient
   Status: In Progress => 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/1277104

Title:
  wrong order of assertEquals args

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Manila:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.policy:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in Python client library for Sahara:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in python-swiftclient:
  Won't Fix
Status in python-troveclient:
  Fix Released
Status in Rally:
  Confirmed
Status in Trove:
  Fix Released

Bug description:
  Args of assertEquals method in ceilometer.tests are arranged in wrong order. 
In result when test fails it shows incorrect information about observed and 
actual data. It's found more than 2000 times.
  Right order of arguments is "expected, actual".

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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/264029
Committed: 
https://git.openstack.org/cgit/openstack/python-solumclient/commit/?id=6559731fb33bddccb364ab8430f6b41b1447f76f
Submitter: Jenkins
Branch:master

commit 6559731fb33bddccb364ab8430f6b41b1447f76f
Author: reedip 
Date:   Wed Jan 6 14:38:55 2016 +0900

Fix argument order for assertEqual to (expected, observed)

assertEqual expects that the arguments provided to it should be (expected, 
observed).
If a particluar order is kept as a convention, then it helps to provide a 
cleaner
message to the developer if Unit Tests fail.
The following patch fixes this issue

TrivialFix

Change-Id: I164dd6b2b820e4ca26bf3406f591ca786893f279
Closes-Bug: #1259292
Closes-Bug: #1277104


** Changed in: python-solumclient
   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/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:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in zaqar:
  Fix Released

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 1536281] [NEW] Missing super() call in some of the Model's subclasses

[Gábor Antal]

Public bug reported:

In model.py, there some subclasses of Model which are not calling the
parent's super() method in their own __init__() method.

The classes are:

VIF8021QbgParams (line 319)
VIF8021QbhParams (line 329)
NetworkInfoAsyncWrapper (line 489)

We need to add super() call to these classes.

** Affects: nova
 Importance: Undecided
 Assignee: Gábor Antal (gabor.antal)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Gábor Antal (gabor.antal)

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

Title:
  Missing super() call in some of the Model's subclasses

Status in OpenStack Compute (nova):
  New

Bug description:
  In model.py, there some subclasses of Model which are not calling the
  parent's super() method in their own __init__() method.

  The classes are:

  VIF8021QbgParams (line 319)
  VIF8021QbhParams (line 329)
  NetworkInfoAsyncWrapper (line 489)

  We need to add super() call to these classes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536281/+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 1536338] [NEW] Fix Ceilometer floating ip pollster

[Pradeep Kilambi]

Public bug reported:

Currently when ceilometer agnt polls for floatingip samples, it talks to
the nova api. But the problem is nova api does not return the
floatingip's for all tenant and filters by current context in this case
is the service tenant for ceilometer. SO the result is always empty.
This is the same behavior in both nova-net as well as neutron scenario.

$ nova floating-ip-list
+++--+--++
| Id | IP | Server Id| Fixed IP | Pool   |
+++--+--++
| 1  | 172.24.4.1 | ef6b7e03-424e-4037-a52d-13e2828f8f98 | 10.0.0.2 | public |
+++--+--++

$ ceilometer meter-list |grep floating
$

Instead the proposal is to use neutron api to poll the floating ip which
gives the right info as expected.

** Affects: ceilometer
 Importance: Undecided
 Assignee: Pradeep Kilambi (pkilambi)
 Status: In Progress

** Changed in: nova
 Assignee: (unassigned) => Pradeep Kilambi (pkilambi)

** Project changed: nova => ceilometer

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

Title:
  Fix Ceilometer floating ip pollster

Status in Ceilometer:
  In Progress

Bug description:
  Currently when ceilometer agnt polls for floatingip samples, it talks
  to the nova api. But the problem is nova api does not return the
  floatingip's for all tenant and filters by current context in this
  case is the service tenant for ceilometer. SO the result is always
  empty. This is the same behavior in both nova-net as well as neutron
  scenario.

  $ nova floating-ip-list
  +++--+--++
  | Id | IP | Server Id| Fixed IP | Pool   |
  +++--+--++
  | 1  | 172.24.4.1 | ef6b7e03-424e-4037-a52d-13e2828f8f98 | 10.0.0.2 | public |
  +++--+--++

  $ ceilometer meter-list |grep floating
  $

  Instead the proposal is to use neutron api to poll the floating ip
  which gives the right info as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1536338/+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 1479569] Re: Output from "role assignment list" is not useful

[Tom Cocozzello]

** Also affects: python-keystoneclient
   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/1479569

Title:
  Output from "role assignment list" is not useful

Status in OpenStack Identity (keystone):
  In Progress
Status in python-keystoneclient:
  In Progress
Status in python-openstackclient:
  In Progress

Bug description:
  It's showing the internal IDs of all the objects, which is really
  unhelpful. It would be much nicer if it showed the actual names of
  users, groups, projects and domains.

  Example:

  $ openstack role assignment list
  
+--+--+--+--+--+
  | Role | User | Group 
   | Project  | Domain  
 |
  
+--+--+--+--+--+
  | 83e948848b7842c9a15e01cfd9db6e1e | 0fa9633d884a42448bbd386778ca6b87 |   
   | 4404002027374bfe878501259b02a5d5 | 
 |
  | 83e948848b7842c9a15e01cfd9db6e1e | 0fa9633d884a42448bbd386778ca6b87 |   
   | 5568fe0e2ca74a5aae35b01f035cdee8 | 
 |
  | f25338bd4a1f4d74927375507d555fa5 | 339e327397d4437d8d1123d63098de76 |   
   | 67e30450f1c44010960aa7e1a457f9b3 | 
 |
  | ecea53c035034e93912428789e8272f6 | 35a3b6d9cb324661b5f144fd60a62964 |   
   | 9b5b2ef803514898b4a3a90ef09dcf66 | 
 |
  | 83e948848b7842c9a15e01cfd9db6e1e | 4644b913eb77414db8f344d37e3da2c2 |   
   | 9b5b2ef803514898b4a3a90ef09dcf66 | 
 |
  | ecea53c035034e93912428789e8272f6 | 50e99a8a5d6c40b2bd973fe55f2cb38b |   
   | 9b5b2ef803514898b4a3a90ef09dcf66 | 
 |
  | f1f56af00ee942a5b24d73dbfe2364cb | 54b9ac936fd04293981b828580a9a3e1 |   
   | 4404002027374bfe878501259b02a5d5 | 
 |
  | f25338bd4a1f4d74927375507d555fa5 | 54b9ac936fd04293981b828580a9a3e1 |   
   | 4404002027374bfe878501259b02a5d5 | 
 |
  | f25338bd4a1f4d74927375507d555fa5 | 54b9ac936fd04293981b828580a9a3e1 |   
   | c02e1e2d94584805a7445b6d31cab364 | 
 |
  | f25338bd4a1f4d74927375507d555fa5 |  | 
96a35e9d12544ee8aa3cfbf05f2fb649 | 4404002027374bfe878501259b02a5d5 |   
   |
  | f25338bd4a1f4d74927375507d555fa5 | 0fa9633d884a42448bbd386778ca6b87 |   
   |  | 
88fc45635a134ef084866fe0fa94e7f3 |
  
+--+--+--+--+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1479569/+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 1534030] Re: Add tox debug env

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266216
Committed: 
https://git.openstack.org/cgit/openstack/python-magnumclient/commit/?id=dfb7d1faf468a86b1eea912504c7dd4a3812c6c4
Submitter: Jenkins
Branch:master

commit dfb7d1faf468a86b1eea912504c7dd4a3812c6c4
Author: ting.wang 
Date:   Tue Jan 12 11:18:22 2016 +0800

Add debug testenv in tox

Once we add debug testenv, we can use "tox -e debug" to debug test cases
when tox is running. Then tox will use oslotest which really debug our
test cases. Only we should do is insert pdb into code.
It's easy to use.

the same in magnum:
https://review.openstack.org/#/c/266020/

Closes-Bug: #1534030
Change-Id: I63ea8086e269b4ecacb7f7e337f1adf2a869db94


** Changed in: python-magnumclient
   Status: In Progress => Fix Released

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

Title:
  Add tox debug env

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Magnum:
  Fix Released
Status in python-magnumclient:
  Fix Released

Bug description:
  Once we add tox debug env in tox.ini , we can debug test cases when
  tox is running.

  In fact, we use oslotest to debug. oslotest is OpenStack Testing Framework 
and Utilities.
  When we run "tox -e debug", tox uses oslotest to debug our test cases.
  links:  http://docs.openstack.org/developer/oslotest/index.html

  Usage:
  insert pdb;pdb.set_trace() into where you want to debug in test cases. And 
then run command "tox -e debug" to break the procedure.
  Details about how to debug, please click this link:
  http://docs.openstack.org/developer/oslotest/features.html

  It's easy to use and convient for us to debug those test cases.

  Meantime, I add [testenv:debug-py27].
  So, we can run "tox -e debug-py27" to designate python env of running debug. 
Just like we run "tox -e py27". In fact, why we run "tox" instead of "run -e 
py27" is that we have written py27 in [tox] envlist  already, so we don't need 
to write it again.
  But we don't need to  write debug in env, so we can write [debug-py27]. 
Actually, It's not necessary, but only to be a little more robust.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1534030/+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 1529193] Re: ec2 credentials create broken in python3

[Brant Knudson]

We've got a blueprint for this, since keystone doesn't claim to support
python 3. https://blueprints.launchpad.net/keystone/+spec/python3

** Changed in: keystone
   Status: New => Won't Fix

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

Title:
  ec2 credentials create broken in python3

Status in OpenStack Identity (keystone):
  Won't Fix

Bug description:
  When I run tools/sample_data.sh, it crashed.

  And the server log is:

  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi Traceback (most 
recent call last):
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi   File 
"/home/zsj/Workspace/openstack/keystone/keystone/common/wsgi.py", line 247, in 
__call__
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi result = 
method(context, **params)
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi   File 
"/home/zsj/Workspace/openstack/keystone/keystone/contrib/ec2/controllers.py", 
line 302, in create_credential
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi tenant_id)
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi   File 
"/home/zsj/Workspace/openstack/keystone/keystone/contrib/ec2/controllers.py", 
line 182, in create_credential
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi credential_id = 
utils.hash_access_key(blob['access'])
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi   File 
"/home/zsj/Workspace/openstack/keystone/keystone/common/utils.py", line 118, in 
hash_access_key
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi 
hash_.update(access)
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi TypeError: 
Unicode-objects must be encoded before hashing
  2015-12-25 15:22:50.568 32700 ERROR keystone.common.wsgi

  related files are:
  
https://github.com/openstack/keystone/blob/507003981206440313cc6fd692ef58c748742435/keystone/contrib/ec2/controllers.py#L182
  
https://github.com/openstack/keystone/blob/507003981206440313cc6fd692ef58c748742435/keystone/common/utils.py#L118

  It will call  utils.hash_access_key to generate a hash.
  However it passes a  Unicode-objects to the function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1529193/+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 1365508] Re: Image type and status are not translated

[Doug Fish]

*** This bug is a duplicate of bug 1415640 ***
https://bugs.launchpad.net/bugs/1415640

** This bug has been marked a duplicate of bug 1415640
   Values for volume, snapshot, and image status are not translatable

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

Title:
  Image type and status are not translated

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  The image type and status are not translated in the Images table.
  There was a previous bug fix for a similar problem but only in the
  Instances table (https://bugs.launchpad.net/horizon/+bug/1224329).
  Seems we could do something similar for image state and type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1365508/+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 1536253] [NEW] nova floating-ip-list - ERROR (ClientException): Unexpected API Error

[Alexandra Kisin]

Public bug reported:

I've installed libverty openstack release on Ubuntu 14.04 with flat network. 
The openstack release is 12.0.0. 

dpkg -l | grep nova-common
ii  nova-common   2:12.0.0-0ubuntu2~cloud0  
  all  OpenStack Compute - common files

Everything seems to work fine, except horizon. 
When I logged in , getting an error message "Error: Unable to retrieve floating 
IP addresses."
Provisioning of VMs is not working in horizon, failed with error. But nova boot 
is working fine and instance is up and running. 
Also when I try to run the commands :
  nova floating-ip-list
ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) 
(Request-ID: req-c088103b-c871-480f-8741-cbb4e9139d05)
 neutron floatingip-list 
404 Not Found
The resource could not be found.

The nova-api.log file is looking as below :
2016-01-20 18:00:46.764 18894 INFO nova.osapi_compute.wsgi.server 
[req-310e6d1a-1a47-43cb-8a86-5a15ceaa9225 9840f0220bfa4542b2edb02958b84f53 
55570ea7c23544f5b572f708390b0471 - - -] 9.148.27.248 "GET /v2/ HTTP/1.1" 
status: 200 len: 572 time: 0.5391979
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
[req-dda981f3-947a-4d05-93fb-180ae2b96d9f 9840f0220bfa4542b2edb02958b84f53 
55570ea7c23544f5b572f708390b0471 - - -] Unexpected exception in API method
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/floating_ips.py", 
line 122, in index
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
floating_ips = self.network_api.get_floating_ips_by_project(context)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 1402, in 
get_floating_ips_by_project
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions fips = 
client.list_floatingips(tenant_id=project_id)['floatingips']
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 102, in 
with_params
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions ret = 
self.function(instance, *args, **kwargs)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 731, in 
list_floatingips
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions **_params)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 307, in 
list
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions for r in 
self._pagination(collection, path, **params):
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 320, in 
_pagination
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions res = 
self.get(path, params=params)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 293, in 
get
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
headers=headers, params=params)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 270, in 
retry_request
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
headers=headers, params=params)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 211, in 
do_request
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
self._handle_fault_response(status_code, replybody)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 185, in 
_handle_fault_response
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
exception_handler_v20(status_code, des_error_body)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 83, in 
exception_handler_v20
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 
message=message)
2016-01-20 18:00:47.098 18894 ERROR nova.api.openstack.extensions 

[Yahoo-eng-team] [Bug 1536258] [NEW] Metadata agent fails when use_ssl is set to True in neutron.conf

[Arnoud de Jonge]

Public bug reported:

The Neutron metadata agent listens on a unix domain socket for requests
coming from Neutron metadata proxies. This communication is done via the
HTTP protocol. When the Neutron Server is configured to use SSL the
use_ssl flag in Neutron will be set to True. As it turns out, this also
affects the Neutron metadata agent.

We use OpenStack Liberty on Ubuntu 14.04 using cloud archive packages.

To reproduce:

Enable SSL in neutron.conf:
use_ssl = True
ssl_cert_file = /etc/neutron/ssl/cert.crt
ssl_key_file = /etc/neutron/ssl/cert.key

Do a request to the Neutron metadata proxy socket:
echo 'GET /' | socat - UNIX-CONNECT:/var/lib/neutron/metadata_proxy

Expected behaviour:
Should return a HTTP 500 error, because of missing headers.

Actual behaviour:
Connection is immediately clossed.

Workaround:
Set 'use_ssl = False' in metadata_agent.ini.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: neutron-metadata-agent

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

Title:
  Metadata agent fails when use_ssl is set to True in neutron.conf

Status in neutron:
  New

Bug description:
  The Neutron metadata agent listens on a unix domain socket for
  requests coming from Neutron metadata proxies. This communication is
  done via the HTTP protocol. When the Neutron Server is configured to
  use SSL the use_ssl flag in Neutron will be set to True. As it turns
  out, this also affects the Neutron metadata agent.

  We use OpenStack Liberty on Ubuntu 14.04 using cloud archive packages.

  To reproduce:

  Enable SSL in neutron.conf:
  use_ssl = True
  ssl_cert_file = /etc/neutron/ssl/cert.crt
  ssl_key_file = /etc/neutron/ssl/cert.key

  Do a request to the Neutron metadata proxy socket:
  echo 'GET /' | socat - UNIX-CONNECT:/var/lib/neutron/metadata_proxy

  Expected behaviour:
  Should return a HTTP 500 error, because of missing headers.

  Actual behaviour:
  Connection is immediately clossed.

  Workaround:
  Set 'use_ssl = False' in metadata_agent.ini.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536258/+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 1323975] Re: do not use default=None for config options

[Tim Hinrichs]

** Changed in: congress
   Status: Fix Committed => Fix Released

** Changed in: congress
Milestone: None => mitaka-2

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

Title:
  do not use default=None for config options

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in Gnocchi:
  Fix Committed
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo-incubator:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in Rally:
  Fix Committed
Status in Sahara:
  Fix Released
Status in tempest:
  In Progress
Status in Trove:
  In Progress
Status in zaqar:
  Fix Released

Bug description:
  In the cfg module default=None is set as the default value. It's not
  necessary to set it again when defining config options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1323975/+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 1536176] Re: network owner cannot get all subnets

[Cedric Brandily]

"""
steps:
1, demo tenant create a network net1
2, demo tenant create a subnet sn1 in net1
3, admin create a subnet sn2 in net1
4, demo tenant run "neutron subnet-list"
expected: command output should contains sn1 and sn2
observed: only sn1 can be seen.
"""

And it seems to be the expected behavior



** Changed in: neutron
   Status: In Progress => Opinion

** Tags added: access-control

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

Title:
  network owner cannot get all subnets

Status in neutron:
  Opinion

Bug description:
  steps:
  1, demo tenant create a network net1
  2, demo tenant create a subnet sn1 in net1
  3, admin create a subnet sn2 in net1
  4, demo tenant run "neutron subnet-list"
  expected: command output should contains sn1 and sn2
  observed: only sn1 can be seen.

  in policy.json
  [1]"create_subnet": "rule:admin_or_network_owner",
  [2]"get_subnet": "rule:admin_or_owner or rule:shared",
  from [1], since only admin and network owner can create subnet on tenant 
network, it should make sense to allow network owner to get all subnets on 
her/his network.

  with rbac, after demo tenant add rbac access_as_shared rule for alt_demo 
tenant.
  alt_demo tenant run "subnet-list" can get sn1 and sn2.
  That's very interesting, rbac allowed tenant can get all subnets, but not 
network owner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536176/+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 1536321] [NEW] cyclic dependencies in implied roles

[Adam Young]

Public bug reported:

Today it is possible to define an implied role structure that is not a
DAG.  This will crash the Keystone server if a token iis requested that
will pull in any of those roles.


While it might be impractical to prevent cycles in the creation, it is
very possible to prevent the expansion from crashing the server.

** 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/1536321

Title:
  cyclic dependencies in implied roles

Status in OpenStack Identity (keystone):
  New

Bug description:
  Today it is possible to define an implied role structure that is not a
  DAG.  This will crash the Keystone server if a token iis requested
  that will pull in any of those roles.


  While it might be impractical to prevent cycles in the creation, it is
  very possible to prevent the expansion from crashing the server.

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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265537
Committed: 
https://git.openstack.org/cgit/openstack/glance_store/commit/?id=120f25e09beebf18df552a79d9fabec81f44a4c7
Submitter: Jenkins
Branch:master

commit 120f25e09beebf18df552a79d9fabec81f44a4c7
Author: LiuNanke 
Date:   Sat Jan 9 20:17:02 2016 +0800

Replace deprecated library function os.popen() with subprocess

os.popen() is deprecated since python 2.6. Resolved with use of
subprocess module.
Closes-Bug: #1529836

Change-Id: Ie98335b65c41906d66abe07989ab014cf079476e


** Changed in: glance-store
   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 bilean:
  In Progress
Status in Blazar:
  In Progress
Status in Ceilometer:
  In Progress
Status in ceilometer-powervm:
  In Progress
Status in Cinder:
  In Progress
Status in congress:
  In Progress
Status in devstack:
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  Fix Released
Status in group-based-policy-specs:
  In Progress
Status in heat:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in horizon-cisco-ui:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kwapi:
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in networking-powervm:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in nova-powervm:
  In Progress
Status in oslo-incubator:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in Python client library for Zaqar:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
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/bilean/+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 1532656] Re: Duplicated content in "Using Glance’s Image Public APIs" page

[Kairat Kushaev]

The first section is related to HEAD request that simply returns image metadata.
The second section is related to GET request that returns image metadata and 
image itself. So the sections are different, not the same. 

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  Duplicated content in "Using Glance’s Image Public APIs" page

Status in Glance:
  Invalid

Bug description:
  In "Using Glance’s Image Public APIs", the content for the section:

  "Retrieve Raw Image Data"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  raw-image-data)

  is simply a dupe of  the section:

  "Retrieve Image Metadata"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  image-metadata)

  Please fix it with the correct documentation for retrieving image
  data.

  Here is the text-snapshot of these two sections in case the live site
  is not available for any reason:
  http://paste.openstack.org/show/483381/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1532656/+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 1536050] [NEW] Error: ImageMetaProps object has no attribute 'ssd'

[yuntongjin]

Public bug reported:

When use AggregateImagePropertiesIsolation scheduler filter, there is : Error: 
ImageMetaProps object has no attribute 'ssd'
Step 1:
create a agg
aggregate-create ssd-agg nova
nova aggregate-set-metadata  ssd-agg  ssd=true
nova aggregate-add-host ssd-agg host-2
Step2. add ssd metadata
nova  image-meta 28565806-241c-43cf-b096-666721748004 set ssd=true
step3: add AggregateImagePropertiesIsolation to nova.conf
step4: boot an instance


Actual result:
 Error: ImageMetaProps object has no attribute 'ssd'

environments:
master stream code

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  Error: ImageMetaProps object has no attribute 'ssd'

Status in OpenStack Compute (nova):
  New

Bug description:
  When use AggregateImagePropertiesIsolation scheduler filter, there is : 
Error: ImageMetaProps object has no attribute 'ssd'
  Step 1:
  create a agg
  aggregate-create ssd-agg nova
  nova aggregate-set-metadata  ssd-agg  ssd=true
  nova aggregate-add-host ssd-agg host-2
  Step2. add ssd metadata
  nova  image-meta 28565806-241c-43cf-b096-666721748004 set ssd=true
  step3: add AggregateImagePropertiesIsolation to nova.conf
  step4: boot an instance

  
  Actual result:
   Error: ImageMetaProps object has no attribute 'ssd'

  environments:
  master stream code

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536050/+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 1530864] Re: VolumeTypeList rest call is not implemented

[Marcos Lobo]

This is already implemented in master
https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/rest/cinder.py#L98

** Changed in: horizon
   Status: New => Invalid

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

Title:
  VolumeTypeList rest call is not implemented

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  VolumeTypeList cinder API REST call is not implemented yet in Horizon

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530864/+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 1536088] [NEW] give net a parameter about launched_at time

[yujie]

Public bug reported:

When we create an instance, it will record the launched_at time. But for net 
and subnet, no such info is provided.
For network manager, the time is important to locate network problems, 
especially when check the log file.
Could we add this info for net and subnet?

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  give net a parameter about launched_at time

Status in neutron:
  New

Bug description:
  When we create an instance, it will record the launched_at time. But for net 
and subnet, no such info is provided.
  For network manager, the time is important to locate network problems, 
especially when check the log file.
  Could we add this info for net and subnet?

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536088/+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 1536087] [NEW] Themes directory should be ignored

[Rob Cresswell]

Public bug reported:

Alternate themes are useful for testing and other customisations. Rather
than using global git excludes or other workarounds, Horizon could just
exclude the themes directory except for the "default" theme and the
alternate "material" example theme.

** Affects: horizon
 Importance: Wishlist
 Assignee: Rob Cresswell (robcresswell)
 Status: In Progress

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

Title:
  Themes directory should be ignored

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  Alternate themes are useful for testing and other customisations.
  Rather than using global git excludes or other workarounds, Horizon
  could just exclude the themes directory except for the "default" theme
  and the alternate "material" example theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536087/+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 1532921] Re: networking-zvm has broken setup.cfg

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266033
Committed: 
https://git.openstack.org/cgit/openstack/networking-zvm/commit/?id=379a8b253a331d0bfb3b775e3bf4d9a0804de087
Submitter: Jenkins
Branch:master

commit 379a8b253a331d0bfb3b775e3bf4d9a0804de087
Author: Andreas Jaeger 
Date:   Mon Jan 11 21:37:30 2016 +0100

Fix setup.cfg packages entry

The packages entry is a python object path, not a file system path. A
"/" is invalid. Fix the entries.

Change-Id: Ibffc582fca82317242accb704ab7f3f52dfe0092
Closes-Bug: #1532921


** Changed in: networking-zvm
   Status: In Progress => 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/1532921

Title:
  networking-zvm has broken setup.cfg

Status in networking-zvm:
  Fix Released
Status in neutron:
  Invalid

Bug description:
  networking-zvm has in setup.cfg:

  [files]
  packages =
  neutron/plugins/zvm
  neutron/plugins/ml2/drivers/zvm

  
  It should have *one* package entry only and it is not allowed to use a "/".

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-zvm/+bug/1532921/+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 1536110] [NEW] OVS agent should fail if can't get DVR mac address

[Oleg Bondarev]

Public bug reported:

If ovs agent is configured to run in dvr mode it has to get it's unique
mac address from server on startup . In case it cannot get it after
several attempts (commit 51303b5fe4785d0cda76f095c95eb4d746d7d783) due
to some error, it falls back to non-dvr mode.

The question is what is the purpoise of ovs agent to be running in non-
dvr mode while it was configured for dvr? Server code does not handle
ovs agent 'in_distributed_mode' flag in any way and will continue
scheduling dvr routers to such nodes. This may lead to connectivity
issues which are hard to debug.

Example:

2016-01-12 11:29:15.186 16238 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_dvr_neutron_agent
[req-e3b3643d-6976-4656-b247-ab291e6a4b27 - - - - -] L2 agent could not
get DVR MAC address at startup due to RPC error.  It happens when the
server does not support this RPC API.  Detailed message: Remote error:
DBConnectionError (_mysql_exceptions.OperationalError) (2013, "Lost
connection to MySQL server at 'reading initial communication packet',
system error: 0")

There were some issues with mysql on startup which led to half of ovs
agents running in non-dvr mode silently.

The proposal is to fail in case agent cannot operate in the mode it was
configured to.

** Affects: neutron
 Importance: Undecided
 Assignee: Oleg Bondarev (obondarev)
 Status: New


** Tags: l3-dvr-backlog

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

Title:
  OVS agent should fail if can't get DVR mac address

Status in neutron:
  New

Bug description:
  If ovs agent is configured to run in dvr mode it has to get it's
  unique mac address from server on startup . In case it cannot get it
  after several attempts (commit
  51303b5fe4785d0cda76f095c95eb4d746d7d783) due to some error, it falls
  back to non-dvr mode.

  The question is what is the purpoise of ovs agent to be running in
  non-dvr mode while it was configured for dvr? Server code does not
  handle ovs agent 'in_distributed_mode' flag in any way and will
  continue scheduling dvr routers to such nodes. This may lead to
  connectivity issues which are hard to debug.

  Example:

  2016-01-12 11:29:15.186 16238 WARNING
  neutron.plugins.ml2.drivers.openvswitch.agent.ovs_dvr_neutron_agent
  [req-e3b3643d-6976-4656-b247-ab291e6a4b27 - - - - -] L2 agent could
  not get DVR MAC address at startup due to RPC error.  It happens when
  the server does not support this RPC API.  Detailed message: Remote
  error: DBConnectionError (_mysql_exceptions.OperationalError) (2013,
  "Lost connection to MySQL server at 'reading initial communication
  packet', system error: 0")

  There were some issues with mysql on startup which led to half of ovs
  agents running in non-dvr mode silently.

  The proposal is to fail in case agent cannot operate in the mode it
  was configured to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536110/+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 1536130] [NEW] error message of "1 is not a supported API version. Example values are 1 or 2." is not precise

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when i add a new api cli command in glance, i get the error message:
"1" is not a supported API version. Example values are "1" or "2".
the reason is i import a wrong module in glanceclient/v1/client.py,
so the return error message is not correct.

it can be recurrent by modifing "from glanceclient.v1.images import 
ImageManager" to 
"from glanceclient.v1.imagesxxx import ImageManager" in 
glanceclient/v1/client.py, then you
execute "glance image-list", you will found it.

** Affects: glance
 Importance: Undecided
 Status: New

-- 
error message of "1 is not a supported API version. Example values are 1 or 2." 
is not precise
https://bugs.launchpad.net/bugs/1536130
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to Glance.

-- 
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 1536130] [NEW] error message of "1 is not a supported API version. Example values are 1 or 2." is not precise

[gs-opencos-zte]

Public bug reported:

when i add a new api cli command in glance, i get the error message:
"1" is not a supported API version. Example values are "1" or "2".
the reason is i import a wrong module in glanceclient/v1/client.py,
so the return error message is not correct.

it can be recurrent by modifing "from glanceclient.v1.images import 
ImageManager" to 
"from glanceclient.v1.imagesxxx import ImageManager" in 
glanceclient/v1/client.py, then you
execute "glance image-list", you will found it.

** Affects: glance
 Importance: Undecided
 Status: New

** Project changed: openstack-community => glance

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

Title:
  error message of "1 is not a supported API version. Example values are
  1 or 2." is not precise

Status in Glance:
  New

Bug description:
  when i add a new api cli command in glance, i get the error message:
  "1" is not a supported API version. Example values are "1" or "2".
  the reason is i import a wrong module in glanceclient/v1/client.py,
  so the return error message is not correct.

  it can be recurrent by modifing "from glanceclient.v1.images import 
ImageManager" to 
  "from glanceclient.v1.imagesxxx import ImageManager" in 
glanceclient/v1/client.py, then you
  execute "glance image-list", you will found it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1536130/+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 1535570] Re: Unexpected API Error in XenServer CI, test_get_console_output_with_unlimited_size

[Bob Ball]

*** This bug is a duplicate of bug 1535616 ***
https://bugs.launchpad.net/bugs/1535616

This is a definite bug; just because it doesn't occur all the time means
it's a race condition that needs to be investigated.


** Changed in: nova
   Status: Invalid => Confirmed

** This bug has been marked a duplicate of bug 1535616
   XenAPI: Console logging race condition

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

Title:
  Unexpected API Error in XenServer CI,
  test_get_console_output_with_unlimited_size

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  There is an error in the XenServer CI tempest test execution:

  2016-01-18 18:48:34.398 | Response - Headers: 
{'x-compute-request-id': 'req-7e306838-35ba-4cb5-b4f5-6e415005f4b9', 'vary': 
'X-OpenStack-Nova-API-Version', 'status': '200', 'content-length': '1578', 
'content-location': 
'http://192.168.33.1:8774/v2.1/d301703afb8848dda9b783f94f29564f/servers/f5a5fe16-eca1-49e5-91b0-14f9d40fa395',
 'date': 'Mon, 18 Jan 2016 18:14:06 GMT', 'content-type': 'application/json', 
'connection': 'close', 'x-openstack-nova-api-version': '2.1'}
  2016-01-18 18:48:34.404 | Body: {"server": {"status": "ACTIVE", 
"updated": "2016-01-18T18:14:06Z", "hostId": 
"87fd95aa5e987035940fc5b72c2ac247e4eb70bbc72689c76cc88125", "addresses": 
{"private": [{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:25:b9:79", "version": 4, 
"addr": "10.1.0.2", "OS-EXT-IPS:type": "fixed"}]}, "links": [{"href": 
"http://192.168.33.1:8774/v2.1/d301703afb8848dda9b783f94f29564f/servers/f5a5fe16-eca1-49e5-91b0-14f9d40fa395;,
 "rel": "self"}, {"href": 
"http://192.168.33.1:8774/d301703afb8848dda9b783f94f29564f/servers/f5a5fe16-eca1-49e5-91b0-14f9d40fa395;,
 "rel": "bookmark"}], "key_name": null, "image": {"id": 
"f6dfe585-26d9-4ec4-8daa-c9ff63ff8431", "links": [{"href": 
"http://192.168.33.1:8774/d301703afb8848dda9b783f94f29564f/images/f6dfe585-26d9-4ec4-8daa-c9ff63ff8431;,
 "rel": "bookmark"}]}, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": 
"active", "OS-SRV-USG:launched_at": "2016-01-18T18:14:05.00", "flavor": 
{"id": "42", "links": [{"href": "http://192
 .168.33.1:8774/d301703afb8848dda9b783f94f29564f/flavors/42", "rel": 
"bookmark"}]}, "id": "f5a5fe16-eca1-49e5-91b0-14f9d40fa395", "security_groups": 
[{"name": "default"}], "OS-SRV-USG:terminated_at": null, 
"OS-EXT-AZ:availability_zone": "nova", "user_id": 
"14ab116a78dc41cfa1c11b0874b157a1", "name": 
"tempest.common.compute-instance-2116796541", "created": 
"2016-01-18T18:13:50Z", "tenant_id": "d301703afb8848dda9b783f94f29564f", 
"OS-DCF:diskConfig": "MANUAL", "os-extended-volumes:volumes_attached": [], 
"accessIPv4": "", "accessIPv6": "", "progress": 100, "OS-EXT-STS:power_state": 
1, "config_drive": "True", "metadata": {}}}
  2016-01-18 18:48:34.410 | 2016-01-18 18:14:06,831 11162 INFO 
[tempest.common.waiters] State transition "BUILD/spawning" ==> "ACTIVE/None" 
after 16 second wait
  2016-01-18 18:48:34.415 | 2016-01-18 18:14:07,375 11162 INFO 
[tempest_lib.common.rest_client] Request 
(ServerActionsTestJSON:test_get_console_output_with_unlimited_size): 500 POST 
http://192.168.33.1:8774/v2.1/d301703afb8848dda9b783f94f29564f/servers/f5a5fe16-eca1-49e5-91b0-14f9d40fa395/action
 0.544s
  2016-01-18 18:48:34.421 | 2016-01-18 18:14:07,376 11162 DEBUG
[tempest_lib.common.rest_client] Request - Headers: {'Content-Type': 
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
  2016-01-18 18:48:34.426 | Body: {"os-getConsoleOutput": {}}
  2016-01-18 18:48:34.432 | Response - Headers: 
{'x-compute-request-id': 'req-08e0d7ce-1501-43fc-87ca-9891fe0a0f6e', 'vary': 
'X-OpenStack-Nova-API-Version', 'status': '500', 'content-length': '194', 
'date': 'Mon, 18 Jan 2016 18:14:07 GMT', 'content-type': 'application/json; 
charset=UTF-8', 'connection': 'close', 'x-openstack-nova-api-version': '2.1'}
  2016-01-18 18:48:34.438 | Body: {"computeFault": {"message": 
"Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ 
and attach the Nova API log if possible.\n", 
"code": 500}}
  2016-01-18 18:48:34.444 | 2016-01-18 18:14:08,846 11162 INFO 
[tempest_lib.common.rest_client] Request 
(ServerActionsTestJSON:test_get_console_output_with_unlimited_size): 500 POST 
http://192.168.33.1:8774/v2.1/d301703afb8848dda9b783f94f29564f/servers/f5a5fe16-eca1-49e5-91b0-14f9d40fa395/action
 0.469s
  2016-01-18 18:48:34.454 | 2016-01-18 18:14:08,847 11162 DEBUG
[tempest_lib.common.rest_client] Request - Headers: {'Content-Type': 
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
  2016-01-18 18:48:34.461 | Body: {"os-getConsoleOutput": {}}
  2016-01-18 18:48:34.468 | Response - Headers: 
{'x-compute-request-id': 'req-4e91c458-e85e-4c6f-8325-8a6fdffef804', 

[Yahoo-eng-team] [Bug 1536176] [NEW] network owner cannot get all subnets

[ZongKai LI]

Public bug reported:

steps:
1, demo tenant create a network net1
2, demo tenant create a subnet sn1 in net1
3, admin create a subnet sn2 in net1
4, demo tenant run "neutron subnet-list"
expected: command output should contains sn1 and sn2
observed: only sn1 can be seen.

in policy.json
[1]"create_subnet": "rule:admin_or_network_owner",
[2]"get_subnet": "rule:admin_or_owner or rule:shared",
from [1], since only admin and network owner can create subnet on tenant 
network, it should make sense to allow network owner to get all subnets on 
her/his network.

** Affects: neutron
 Importance: Undecided
 Assignee: ZongKai LI (lzklibj)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => ZongKai LI (lzklibj)

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

Title:
  network owner cannot get all subnets

Status in neutron:
  New

Bug description:
  steps:
  1, demo tenant create a network net1
  2, demo tenant create a subnet sn1 in net1
  3, admin create a subnet sn2 in net1
  4, demo tenant run "neutron subnet-list"
  expected: command output should contains sn1 and sn2
  observed: only sn1 can be seen.

  in policy.json
  [1]"create_subnet": "rule:admin_or_network_owner",
  [2]"get_subnet": "rule:admin_or_owner or rule:shared",
  from [1], since only admin and network owner can create subnet on tenant 
network, it should make sense to allow network owner to get all subnets on 
her/his network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1536176/+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 1525809] Re: networking-midonet 2015.1.2 stable/kilo release request

[YAMAMOTO Takashi]

** Changed in: networking-midonet
   Status: New => 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/1525809

Title:
   networking-midonet 2015.1.2 stable/kilo release request

Status in networking-midonet:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  please push 2015.1.2 tag on the tip of stable/kilo.
  namely, commit 69c7c61e1cf9934bfdaac6774e2f02a2aa5d5472  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1525809/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

[OpenStack Infra]

Reviewed:  https://review.openstack.org/268901
Committed: 
https://git.openstack.org/cgit/openstack/congress/commit/?id=0e65d5f9208f6031343b11770e555715a8bf5518
Submitter: Jenkins
Branch:master

commit 0e65d5f9208f6031343b11770e555715a8bf5518
Author: vishal mahajan 
Date:   Mon Jan 18 12:52:19 2016 +0530

Replace assertEqual(*, None) with assertIsNone in tests.

For more clear messages in case of failure.
Closes-bug: #1280522

Change-Id: Icd110ab619dc500cd6bb10137e4f839812533f7b


** Changed in: congress
   Status: Fix Committed => 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/1280522

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

Status in Anchor:
  Fix Released
Status in bifrost:
  Fix Committed
Status in Blazar:
  In Progress
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in dox:
  New
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in heat:
  Fix Released
Status in heat-cfntools:
  Fix Released
Status in Heat Translator:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in kolla-mesos:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in ooi:
  In Progress
Status in os-client-config:
  Fix Released
Status in python-barbicanclient:
  In Progress
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-cueclient:
  Fix Released
Status in python-designateclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  In Progress
Status in OpenStack SDK:
  In Progress
Status in python-swiftclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in refstack:
  In Progress
Status in Sahara:
  Fix Released
Status in Solum:
  Fix Released
Status in Stackalytics:
  In Progress
Status in tempest:
  Fix Released
Status in Trove:
  Fix Released
Status in tuskar:
  Fix Released
Status in zaqar:
  Fix Released
Status in designate package in Ubuntu:
  New
Status in python-tuskarclient package in Ubuntu:
  Fix Committed

Bug description:
  Replace assertEqual(None, *) with assertIsNone in tests to have
  more clear messages in case of failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1533518] Re: Remove 'validate' key in 'type:dict_or_nodata' type in resource attribute map

[OpenStack Infra]

Reviewed:  https://review.openstack.org/266319
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=d3701f001d7e6f9d4af8521354c1a84accd6e830
Submitter: Jenkins
Branch:master

commit d3701f001d7e6f9d4af8521354c1a84accd6e830
Author: Bo Chi 
Date:   Wed Jan 13 03:15:53 2016 -0500

Remove 'validate' key in 'type:dict_or_nodata' type

In resource_map dict, if the 'validate' section of type:dict_or_nodata
contains 'validate' key, the validation will not be performed correctly,
because in _validate_dict_item(), it checks key name that starts with
'type:', and perform the validation.

This patch removed 'validate' key in 'external_fixed_ips' section in
neutron/extensions/l3_ext_gw_mode.py

Change-Id: I1ee49f8313bddef6f41b133f49830a8fbbe4769e
Closes-Bug: #1533518


** 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 neutron.
https://bugs.launchpad.net/bugs/1533518

Title:
  Remove 'validate' key in 'type:dict_or_nodata' type in resource
  attribute map

Status in neutron:
  Fix Released

Bug description:
  In neutron/extensions/l3_ext_gw_mode.py, there's another 'validate' key in 
the 'validate' section of type 'type:dict_or_nodata', this cause the validation 
is not performed.
  Because in _validate_dict_item(), it checks key name that starts with 
'type:', and perform the validation.

  EXTENDED_ATTRIBUTES_2_0 = { 
  'routers': {l3.EXTERNAL_GW_INFO:
  {'allow_post': True,
   'allow_put': True,
   'is_visible': True,
   'default': None,
   'enforce_policy': True,
   'validate':
   {'type:dict_or_nodata':
{'network_id': {'type:uuid': None, 'required': True},
 'enable_snat': {'type:boolean': None, 'required': False,
 'convert_to': attrs.convert_to_boolean},
 'external_fixed_ips': {
 'convert_list_to': attrs.convert_kvp_list_to_dict,
 'validate': {'type:fixed_ips': None},  
  < error
 'default': None,
 'required': False}
 }   


  The correct format is :

  'external_fixed_ips': {
 'convert_list_to': attrs.convert_kvp_list_to_dict,
 'type:fixed_ips': None,
< should be
 'default': None,
 'required': False}
 }

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