[Yahoo-eng-team] [Bug 1302351] [NEW] v2 API can't create image - Attribute 'file' is reserved.
Public bug reported: Trying to create an image with V2 API and get the following error: glance --os-image-api-version 2 --os-image-url http://glance-icehouse:9292/ image-create --container-format bare --disk-format raw --name trusty2 --file trusty-server-cloudimg-amd64-disk1.img Request returned failure status. 403 Forbidden Attribute 'file' is reserved. (HTTP 403) It works fine if I do --os-image-api-version 1 ** Affects: glance Importance: Undecided Status: New ** Summary changed: - v2 API can't create image + v2 API can't create image - Attribute 'file' is reserved. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302351 Title: v2 API can't create image - Attribute 'file' is reserved. Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Trying to create an image with V2 API and get the following error: glance --os-image-api-version 2 --os-image-url http://glance-icehouse:9292/ image-create --container-format bare --disk-format raw --name trusty2 --file trusty-server-cloudimg-amd64-disk1.img Request returned failure status. 403 Forbidden Attribute 'file' is reserved. (HTTP 403) It works fine if I do --os-image-api-version 1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302351/+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 1302367] [NEW] The session timed out message is shown when tried to relogin
Public bug reported: Description : When tried to access the horizon due to idle session, it redirects to the login page. After entering the username and password it first gives the message Session timed out, and then again asks for the credentials to login. Expected : Due to idle session, it should redirects to the login page and then just on providing the credentials it should login instead of giving the session timed out message and again asking for credentials. Build Used -- Icehouse root@os-controller:~/horizon-pkg# dpkg -l | grep -i django ii openstack-dashboard 1:2014.1+git201403311756~precise-0ubuntu1 django web interface to Openstack ii python-django-horizon1:2014.1+git201403311756~precise-0ubuntu1 Django module providing web based interaction with OpenStack ii python-django-openstack 1:2014.1+git201403311756~precise-0ubuntu1 dummy transitonal package ** Affects: horizon Importance: Undecided Status: New ** Attachment added: openstack_horizon_idle_session.jpg https://bugs.launchpad.net/bugs/1302367/+attachment/4064794/+files/openstack_horizon_idle_session.jpg -- 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/1302367 Title: The session timed out message is shown when tried to relogin Status in OpenStack Dashboard (Horizon): New Bug description: Description : When tried to access the horizon due to idle session, it redirects to the login page. After entering the username and password it first gives the message Session timed out, and then again asks for the credentials to login. Expected : Due to idle session, it should redirects to the login page and then just on providing the credentials it should login instead of giving the session timed out message and again asking for credentials. Build Used -- Icehouse root@os-controller:~/horizon-pkg# dpkg -l | grep -i django ii openstack-dashboard 1:2014.1+git201403311756~precise-0ubuntu1 django web interface to Openstack ii python-django-horizon 1:2014.1+git201403311756~precise-0ubuntu1 Django module providing web based interaction with OpenStack ii python-django-openstack 1:2014.1+git201403311756~precise-0ubuntu1 dummy transitonal package To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1302367/+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 1302384] [NEW] Requires refresh browser on deleting the Instance
Public bug reported: Release -- Icehouse Builds Used root@os-controller:~/horizon-pkg# dpkg -l | grep -i django ii openstack-dashboard 1:2014.1+git201403311756~precise-0ubuntu1 django web interface to Openstack ii python-django-horizon1:2014.1+git201403311756~precise-0ubuntu1 Django module providing web based interaction with OpenStack ii python-django-openstack 1:2014.1+git201403311756~precise-0ubuntu1 dummy transitonal package Problem Description : The instance on deletion still appears on the Instances page, its entry gets clear only on clicking the browser refresh button. Steps 1. On Horizon Instances page, select the instance on deletion. 2. Clicked the Terminate Instance Button. It gives message Success: Scheduled termination of Instance 3. Observed the deleted instance entry is still appearing. 4. Only on clicking the browser refresh button, the deleted instance entry gets removed. This behavior creates confusion, it seems like instance is not deleted and if again try to terminate the same instance it gives error message Error : you are not allowed to terminate the instance :vm-a1. In this case even when we refresh the browser the entry of the deleted instance remains present. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Redeleting_the_deleted_instance.jpg https://bugs.launchpad.net/bugs/1302384/+attachment/4064866/+files/Redeleting_the_deleted_instance.jpg -- 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/1302384 Title: Requires refresh browser on deleting the Instance Status in OpenStack Dashboard (Horizon): New Bug description: Release -- Icehouse Builds Used root@os-controller:~/horizon-pkg# dpkg -l | grep -i django ii openstack-dashboard 1:2014.1+git201403311756~precise-0ubuntu1 django web interface to Openstack ii python-django-horizon 1:2014.1+git201403311756~precise-0ubuntu1 Django module providing web based interaction with OpenStack ii python-django-openstack 1:2014.1+git201403311756~precise-0ubuntu1 dummy transitonal package Problem Description : The instance on deletion still appears on the Instances page, its entry gets clear only on clicking the browser refresh button. Steps 1. On Horizon Instances page, select the instance on deletion. 2. Clicked the Terminate Instance Button. It gives message Success: Scheduled termination of Instance 3. Observed the deleted instance entry is still appearing. 4. Only on clicking the browser refresh button, the deleted instance entry gets removed. This behavior creates confusion, it seems like instance is not deleted and if again try to terminate the same instance it gives error message Error : you are not allowed to terminate the instance :vm-a1. In this case even when we refresh the browser the entry of the deleted instance remains present. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1302384/+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 1302387] [NEW] Allow changing any horizon settings from the plugin config files
Public bug reported: Dashboard can now load any number of additional configuration files that add, remove or modify dashboards and their configuration. Sometimes, however, the panels need to also modify some of the HORIZON_CONFIG values that are not supported by this mechanism. We need a way to override arbitrary HORIZON_CONFIG values from the dashboard configuration files. ** Affects: horizon Importance: Undecided Assignee: Radomir Dopieralski (thesheep) 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/1302387 Title: Allow changing any horizon settings from the plugin config files Status in OpenStack Dashboard (Horizon): In Progress Bug description: Dashboard can now load any number of additional configuration files that add, remove or modify dashboards and their configuration. Sometimes, however, the panels need to also modify some of the HORIZON_CONFIG values that are not supported by this mechanism. We need a way to override arbitrary HORIZON_CONFIG values from the dashboard configuration files. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1302387/+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 1302390] [NEW] whitelist_externals = bash in tox.ini should be pep8 section
Public bug reported: Commit 085a35d657cf0fa41a402f2af66c4beaa0f60db2 fixes translation jobs, but whitelist_externals = bash is added to the wrong section. It should be not in functional section but pep8 section in tox.ini. ** Affects: neutron Importance: Undecided Assignee: Akihiro Motoki (amotoki) 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/1302390 Title: whitelist_externals = bash in tox.ini should be pep8 section Status in OpenStack Neutron (virtual network service): New Bug description: Commit 085a35d657cf0fa41a402f2af66c4beaa0f60db2 fixes translation jobs, but whitelist_externals = bash is added to the wrong section. It should be not in functional section but pep8 section in tox.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302390/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1280105] Re: urllib/urllib2 is incompatible for python 3
** Changed in: sahara Status: Fix Committed = Fix Released ** Changed in: sahara Milestone: None = icehouse-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1280105 Title: urllib/urllib2 is incompatible for python 3 Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in OpenStack Data Processing (Sahara, ex. Savanna): Fix Released Status in Tempest: In Progress Status in Trove - Database as a Service: In Progress Status in Zuul: A project gating system: In Progress Bug description: urllib/urllib2 is incompatible for python 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1280105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1229324] Re: extraneous vim editor configuration comments
This bug has now too many tasks, so we can't update those anymore (boo LP). The only way to make them disappear is to delete the tasks entirely. Keystone, Trove and Sahara were fixed and released, i'm removing them so that they don't appear FixCommitted anymore. ** No longer affects: sahara ** No longer affects: keystone ** No longer affects: trove -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1229324 Title: extraneous vim editor configuration comments Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Hacking Guidelines: In Progress Status in Orchestration API (Heat): In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic (Bare Metal Provisioning): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Ceilometer: In Progress Status in Python client library for Cinder: In Progress Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Committed Status in Python client library for Ironic: In Progress Status in Python client library for Keystone: Fix Committed Status in Python client library for Neutron: In Progress Status in Python client library for Swift: In Progress Status in Trove client binding: In Progress Status in Storyboard database creator: New Status in OpenStack Object Storage (Swift): In Progress Status in Taskflow for task-oriented systems.: In Progress Status in Tempest: Fix Released Status in Tuskar: In Progress Bug description: Many of the source code files have a beginning line # vim: tabstop=4 shiftwidth=4 softtabstop=4 This should be deleted. Many of these lines are in the ceilometer/openstack/common directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1229324/+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 1231339] Re: keystone s3_token middleware not usable
** Changed in: swift (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1231339
Title:
keystone s3_token middleware not usable
Status in OpenStack Identity (Keystone):
Fix Released
Status in Python client library for Keystone:
Invalid
Status in “swift” package in Ubuntu:
Fix Released
Bug description:
s3 middleware authentication is causing swift-proxy server to fail to
start:
proxy-server (21880) appears to have stopped
Starting proxy-server...(/etc/swift/proxy-server.conf)
Traceback (most recent call last):
File /usr/bin/swift-proxy-server, line 22, in module
run_wsgi(conf_file, 'proxy-server', default_port=8080, **options)
File /usr/lib/python2.7/dist-packages/swift/common/wsgi.py, line 256, in
run_wsgi
loadapp(conf_path, global_conf={'log_name': log_name})
File /usr/lib/python2.7/dist-packages/swift/common/wsgi.py, line 107, in
wrapper
return f(conf_uri, *args, **kwargs)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 247,
in loadapp
return loadobj(APP, uri, name=name, **kw)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 271,
in loadobj
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 296,
in loadcontext
global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 320,
in _loadconfig
return loader.get_context(object_type, name, global_conf)
File /usr/lib/python2.7/dist-packages/swift/common/wsgi.py, line 55, in
get_context
object_type, name=name, global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 450,
in get_context
global_additions=global_additions)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 562,
in _pipeline_app_context
for name in pipeline[:-1]]
File /usr/lib/python2.7/dist-packages/swift/common/wsgi.py, line 55, in
get_context
object_type, name=name, global_conf=global_conf)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 458,
in get_context
section)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 517,
in _context_from_explicit
value = import_string(found_expr)
File /usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py, line 22,
in import_string
return pkg_resources.EntryPoint.parse(x= + s).load(False)
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2015, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File /usr/lib/python2.7/dist-packages/keystone/middleware/__init__.py,
line 18, in module
from keystone.middleware.core import *
File /usr/lib/python2.7/dist-packages/keystone/middleware/core.py, line
21, in module
from keystone.common import utils
File /usr/lib/python2.7/dist-packages/keystone/common/utils.py, line 32,
in module
from keystone import exception
File /usr/lib/python2.7/dist-packages/keystone/exception.py, line 63, in
module
class ValidationError(Error):
File /usr/lib/python2.7/dist-packages/keystone/exception.py, line 64, in
ValidationError
message_format = _(Expecting to find %(attribute)s in %(target)s.
NameError: name '_' is not defined
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: swift-proxy 1.9.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Thu Sep 26 09:14:50 2013
Ec2AMI: ami-0092
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: swift
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1231339/+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 1302452] [NEW] nova unshelve VM failed
Public bug reported: I boot a vm with '--boot-volume volume_id ', then shelve this VM, nova return success, but doesn't upload image to glance, then I unshelve this vm, it will failed and this VM'state is unshelving, so I think a VM which is booted from volume_id is not allowed shelve! the error log in nova-conductor is bellow: Traceback (most recent call last): File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/amqp.py, line 461, in _process_data **args) File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py, line 172, in dispatch result = getattr(proxyobj, method)(ctxt, **kwargs) File /usr/lib64/python2.6/site-packages/nova/conductor/manager.py, line 797, in unshelve_instance sys_meta['shelved_image_id']) KeyError: 'shelved_image_id' ** Affects: nova Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New ** Changed in: nova Assignee: (unassigned) = shihanzhang (shihanzhang) ** Description changed: I boot a vm with '--boot-volume volume_id ', then shelve this VM, nova return success, but doesn't upload image to glance, then I unshelve this vm, it will failed and this VM'state is unshelving, so I think a VM which is booted from volume_id is not allowed shelve! + + the error log in nova-conductor is bellow: + Traceback (most recent call last): +File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/amqp.py, line 461, in _process_data + **args) +File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py, line 172, in dispatch + result = getattr(proxyobj, method)(ctxt, **kwargs) +File /usr/lib64/python2.6/site-packages/nova/conductor/manager.py, line 797, in unshelve_instance + sys_meta['shelved_image_id']) + KeyError: 'shelved_image_id' -- 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/1302452 Title: nova unshelve VM failed Status in OpenStack Compute (Nova): New Bug description: I boot a vm with '--boot-volume volume_id ', then shelve this VM, nova return success, but doesn't upload image to glance, then I unshelve this vm, it will failed and this VM'state is unshelving, so I think a VM which is booted from volume_id is not allowed shelve! the error log in nova-conductor is bellow: Traceback (most recent call last): File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/amqp.py, line 461, in _process_data **args) File /usr/lib64/python2.6/site-packages/nova/openstack/common/rpc/dispatcher.py, line 172, in dispatch result = getattr(proxyobj, method)(ctxt, **kwargs) File /usr/lib64/python2.6/site-packages/nova/conductor/manager.py, line 797, in unshelve_instance sys_meta['shelved_image_id']) KeyError: 'shelved_image_id' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302452/+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 1302463] [NEW] LinuxBridgeManager is not using device_exist from ip_lib
Public bug reported: LinuxBridgeManager is adding a new method for checking the existence of a device instead of using the one in ip_lib ** Affects: neutron Importance: Undecided Assignee: Rossella Sblendido (rossella-o) Status: In Progress ** Changed in: neutron Assignee: (unassigned) = Rossella Sblendido (rossella-o) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302463 Title: LinuxBridgeManager is not using device_exist from ip_lib Status in OpenStack Neutron (virtual network service): In Progress Bug description: LinuxBridgeManager is adding a new method for checking the existence of a device instead of using the one in ip_lib To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302463/+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 1302467] [NEW] Logging on list operations slows down operation by about 500%
Public bug reported: On list operations, every attribute for every item returned by the plugin is checked by the policy engine to see whether the user has rights to see it [*], assuming the attribute map specifies enforce_policy=True for that attribute However, in most cases no policies are actually defined for those attributes; in this case the neutron server emits a log.debug statement for the specific attribute saying no policy was found. This statement is then repeated for every attribute without policy times the number of items in the response. Simple instrumenation shows list operations take in the API layer more than 500% the time they take in the plugin. The time is wasted after the plugin call completes and more precisely while doing policy checks. While other optimisations might be performed (such as not repeating checks already performed, and not triggering init() for each check), the biggest offender is the log statement. Some measurements are available here: http://paste.openstack.org/show/75069/ * I believe this is wrong as well, but that's another story ** Affects: neutron Importance: High Assignee: Salvatore Orlando (salvatore-orlando) Status: In Progress ** Tags: api icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302467 Title: Logging on list operations slows down operation by about 500% Status in OpenStack Neutron (virtual network service): In Progress Bug description: On list operations, every attribute for every item returned by the plugin is checked by the policy engine to see whether the user has rights to see it [*], assuming the attribute map specifies enforce_policy=True for that attribute However, in most cases no policies are actually defined for those attributes; in this case the neutron server emits a log.debug statement for the specific attribute saying no policy was found. This statement is then repeated for every attribute without policy times the number of items in the response. Simple instrumenation shows list operations take in the API layer more than 500% the time they take in the plugin. The time is wasted after the plugin call completes and more precisely while doing policy checks. While other optimisations might be performed (such as not repeating checks already performed, and not triggering init() for each check), the biggest offender is the log statement. Some measurements are available here: http://paste.openstack.org/show/75069/ * I believe this is wrong as well, but that's another story To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302467/+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 1302480] [NEW] Nova boot fails when there is a Dummy datacenter in the vCenter
*** This bug is a duplicate of bug 1302482 *** https://bugs.launchpad.net/bugs/1302482 Public bug reported: when there is a Datacenter with no host , i.e an empty cluster, nova boot fails. The scheduler log error trace Error from last host: devstack (node domain-c162(Demo-1)): [u'Traceback (most recent call last):\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1322, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 399, in decorated_function\n return function(self, context, *args, **kwargs)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1734, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /opt/stack/nova/nova/openstack/common/excutils.py, line 68, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1731, in _spawn\n block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 619, in spawn\n admin_password, network_info, block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 211, in spawn\ndc_info = self.get_datacenter_ref_ and_name(data_store_ref)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1715, in get_datacenter_ref_and_name\n self._update_datacenter_cache_from_objects(dcs)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1693, in _update_datacenter_cache_from_objects\ndatastore_refs = p.val.ManagedObjectReference\n', uAttributeError: 'Text' object has no attribute 'ManagedObjectReference'\n] 2014-04-04 03:05:41.629 WARNING nova.scheduler.driver [req-cc690e5a-2bf3-4566-a697-30ca882df815 nova service] [instance: f0abb23a-943a-475d-ac63-69d2563362cb] Setting instance to ERROR state ** Affects: nova Importance: Undecided Status: New ** Tags: openstack-compute -- 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/1302480 Title: Nova boot fails when there is a Dummy datacenter in the vCenter Status in OpenStack Compute (Nova): New Bug description: when there is a Datacenter with no host , i.e an empty cluster, nova boot fails. The scheduler log error trace Error from last host: devstack (node domain-c162(Demo-1)): [u'Traceback (most recent call last):\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1322, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 399, in decorated_function\n return function(self, context, *args, **kwargs)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1734, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /opt/stack/nova/nova/openstack/common/excutils.py, line 68, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1731, in _spawn\n block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 619, in spawn\n admin_password, network_info, block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 211, in spawn\ndc_info = self.get_datacenter_re f_and_name(data_store_ref)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1715, in get_datacenter_ref_and_name\n self._update_datacenter_cache_from_objects(dcs)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1693, in _update_datacenter_cache_from_objects\ndatastore_refs = p.val.ManagedObjectReference\n', uAttributeError: 'Text' object has no attribute 'ManagedObjectReference'\n] 2014-04-04 03:05:41.629 WARNING nova.scheduler.driver [req-cc690e5a-2bf3-4566-a697-30ca882df815 nova service] [instance: f0abb23a-943a-475d-ac63-69d2563362cb] Setting instance to ERROR state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302480/+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 1302482] [NEW] VMware driver: Nova boot fails when there is an empty datacenter in the vCenter
Public bug reported: when there is a Datacenter with no host , i.e an empty cluster, nova boot fails. The scheduler log error trace Error from last host: devstack (node domain-c162(Demo-1)): [u'Traceback (most recent call last):\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1322, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 399, in decorated_function\n return function(self, context, *args, **kwargs)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1734, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /opt/stack/nova/nova/openstack/common/excutils.py, line 68, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1731, in _spawn\n block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 619, in spawn\n admin_password, network_info, block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 211, in spawn\ndc_info = self.get_datacenter_ref_ and_name(data_store_ref)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1715, in get_datacenter_ref_and_name\n self._update_datacenter_cache_from_objects(dcs)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1693, in _update_datacenter_cache_from_objects\ndatastore_refs = p.val.ManagedObjectReference\n', uAttributeError: 'Text' object has no attribute 'ManagedObjectReference'\n] 2014-04-04 03:05:41.629 WARNING nova.scheduler.driver [req-cc690e5a-2bf3-4566-a697-30ca882df815 nova service] [instance: f0abb23a-943a-475d-ac63-69d2563362cb] Setting instance to ERROR state. ** Affects: nova Importance: Undecided Assignee: Chinmaya Bharadwaj (acbharadwaj) Status: New ** Tags: vmware ** Changed in: nova Assignee: (unassigned) = Chinmaya Bharadwaj (acbharadwaj) ** Summary changed: - Nova boot fails when there is a Dummy datacenter in the vCenter + Nova boot fails when there is an empty datacenter in the vCenter ** Summary changed: - Nova boot fails when there is an empty datacenter in the vCenter + VMware driver: Nova boot fails when there is an empty datacenter in the vCenter -- 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/1302482 Title: VMware driver: Nova boot fails when there is an empty datacenter in the vCenter Status in OpenStack Compute (Nova): New Bug description: when there is a Datacenter with no host , i.e an empty cluster, nova boot fails. The scheduler log error trace Error from last host: devstack (node domain-c162(Demo-1)): [u'Traceback (most recent call last):\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1322, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 399, in decorated_function\n return function(self, context, *args, **kwargs)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1734, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /opt/stack/nova/nova/openstack/common/excutils.py, line 68, in __exit__\n six.reraise(self.type_, self.value, self.tb)\n', u' File /opt/stack/nova/nova/compute/manager.py, line 1731, in _spawn\n block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/driver.py, line 619, in spawn\n admin_password, network_info, block_device_info)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 211, in spawn\ndc_info = self.get_datacenter_re f_and_name(data_store_ref)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1715, in get_datacenter_ref_and_name\n self._update_datacenter_cache_from_objects(dcs)\n', u' File /opt/stack/nova/nova/virt/vmwareapi/vmops.py, line 1693, in _update_datacenter_cache_from_objects\ndatastore_refs = p.val.ManagedObjectReference\n', uAttributeError: 'Text' object has no attribute 'ManagedObjectReference'\n] 2014-04-04 03:05:41.629 WARNING nova.scheduler.driver [req-cc690e5a-2bf3-4566-a697-30ca882df815 nova service] [instance: f0abb23a-943a-475d-ac63-69d2563362cb] Setting instance to ERROR state. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302482/+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 1302490] [NEW] Requirements fail to be synced in milestone-proposed
Public bug reported: With our current process around openstack/requirements, no requirements sync is ever pushed to milestone-proposed branches. None is proposed until the openstack/requirements MP branch is created, and when it is, the propose-requirements job fails with: git review -t openstack/requirements milestone-proposed + OUTPUT='Had trouble running git log --color=auto --decorate --oneline milestone-proposed --not remotes/gerrit/milestone-proposed fatal: ambiguous argument '\''milestone-proposed'\'': unknown revision or path not in the working tree. Use '\''--'\'' to separate paths from revisions' See https://jenkins.openstack.org/job/propose-requirements- updates/153/console as an example (while it lasts) ** Affects: ceilometer Importance: Undecided Status: New ** Affects: cinder Importance: Undecided Status: New ** Affects: glance Importance: Undecided Status: New ** Affects: heat Importance: Undecided Status: New ** Affects: ironic Importance: Undecided Status: New ** Affects: keystone Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** Affects: openstack-ci Importance: Undecided Status: New ** Affects: swift Importance: Undecided Status: New ** Tags: icehouse-rc-potential ** Also affects: ceilometer Importance: Undecided Status: New ** Also affects: cinder Importance: Undecided Status: New ** Also affects: glance Importance: Undecided Status: New ** Also affects: heat Importance: Undecided Status: New ** Also affects: ironic Importance: Undecided Status: New ** Also affects: keystone Importance: Undecided Status: New ** Also affects: neutron Importance: Undecided Status: New ** Also affects: swift Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302490 Title: Requirements fail to be synced in milestone-proposed Status in OpenStack Telemetry (Ceilometer): New Status in Cinder: New Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): New Status in Ironic (Bare Metal Provisioning): New Status in OpenStack Identity (Keystone): New Status in OpenStack Neutron (virtual network service): New Status in OpenStack Core Infrastructure: New Status in OpenStack Object Storage (Swift): New Bug description: With our current process around openstack/requirements, no requirements sync is ever pushed to milestone-proposed branches. None is proposed until the openstack/requirements MP branch is created, and when it is, the propose-requirements job fails with: git review -t openstack/requirements milestone-proposed + OUTPUT='Had trouble running git log --color=auto --decorate --oneline milestone-proposed --not remotes/gerrit/milestone-proposed fatal: ambiguous argument '\''milestone-proposed'\'': unknown revision or path not in the working tree. Use '\''--'\'' to separate paths from revisions' See https://jenkins.openstack.org/job/propose-requirements- updates/153/console as an example (while it lasts) To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1302490/+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 1302532] Re: docs build for django-based projects should run with DJANGO_SETTINGS_MODULE envvar
My plan is: - to add docs env which defines DJANGO_SETTINGS_MODULE and runs build_sphinx to tox.ini in Horizon and Django OpenStack auth. - fix run_docs.sh in slave_scripts to use tox -edocs rather than tox -evenv ** Changed in: openstack-ci Assignee: (unassigned) = Akihiro Motoki (amotoki) ** Also affects: horizon Importance: Undecided Status: New ** Also affects: django-openstack-auth Importance: Undecided Status: New ** Changed in: horizon Assignee: (unassigned) = Akihiro Motoki (amotoki) ** Changed in: django-openstack-auth Assignee: (unassigned) = Akihiro Motoki (amotoki) ** Changed in: horizon Importance: Undecided = Medium ** Changed in: django-openstack-auth Importance: Undecided = Medium -- 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/1302532 Title: docs build for django-based projects should run with DJANGO_SETTINGS_MODULE envvar Status in Django OpenStack Auth: New Status in OpenStack Dashboard (Horizon): New Status in OpenStack Core Infrastructure: New Bug description: When running docs build in the gate and post jobs for django-based projects (e.g., horizon, django_openstack_auth, ...), we need to set DJANGO_SETTINGS_MODULE envvar. We can see the following errors in console logs: horizon-docs, gate-horizon-docs: ImproperlyConfigured: The SECRET_KEY setting must not be empty. https://jenkins.openstack.org/view/All/job/horizon-docs/ https://jenkins.openstack.org/view/All/job/gate-horizon-docs/ django-openstack-auth: error: invalid command 'build_sphinx' ERROR: InvocationError: '/home/jenkins/workspace/gate-django_openstack_auth-docs/.tox/venv/bin/python setup.py build_sphinx' It also comes from lack of DJANGO_SETTINGS_MODULES. https://jenkins.openstack.org/view/All/job/gate-django_openstack_auth-docs/ https://jenkins.openstack.org/view/All/job/django_openstack_auth-docs/ To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1302532/+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 1302545] [NEW] Boot volumes API race
Public bug reported: When there is a race for a volume between 2 or more instances, it is possible for more than one to pass the API check. All of them will get scheduled as a result, and only one will actually successfully attach the volume, while others will go to ERROR. This is not ideal since we can reserve the volume in the API, thus making it a bit more user friendly when there is a race (the user will be informed immediately instead of seeing an errored instance). ** Affects: nova Importance: Low Status: Triaged ** Tags: 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/1302545 Title: Boot volumes API race Status in OpenStack Compute (Nova): Triaged Bug description: When there is a race for a volume between 2 or more instances, it is possible for more than one to pass the API check. All of them will get scheduled as a result, and only one will actually successfully attach the volume, while others will go to ERROR. This is not ideal since we can reserve the volume in the API, thus making it a bit more user friendly when there is a race (the user will be informed immediately instead of seeing an errored instance). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302545/+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 1301036] Re: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration
** Changed in: oslo Status: In Progress = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1301036 Title: openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): Triaged Status in Ironic (Bare Metal Provisioning): Invalid Status in OpenStack Identity (Keystone): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in “keystone” package in Ubuntu: Triaged Status in “keystone” source package in Trusty: Triaged Bug description: The code in openstack.common.db.sqlachemy.migration that does the sanity checking on the UTF8 table is a bit overzealous and checks the migration_version (and alembic equivalent) table for utf8 status. This will cause migrations to fail in any case where the db isn't forcing a default character set of utf8, the db engine isn't forced to utf8, or the migration_version table isn't fixed before migrations occur. This was duplicated by doing a clean Ubuntu 12.04 install with mysql, using the default latin1 character set and simply creating the DB with ``create database keystone;`` The result is migrations fail at migration 0 unless the db sanity check is disabled (e.g. glance). root@precise64:~/keystone# keystone-manage --config-file /etc/keystone.conf db_sync 2014-04-01 14:03:23.858 19840 CRITICAL keystone [-] ValueError: Tables migrate_version have non utf8 collation, please make sure all tables are CHARSET=utf8 This is unaffected by the character set in the connection string. The solution is to explicitly ignore the migrate_version (and alembic equivalent) table in the sanity check. Code in question is here: http://git.openstack.org/cgit/openstack/keystone/tree/keystone/openstack/common/db/sqlalchemy/migration.py?id=51772e1addf8ab6f7483df44b7243fd7842eba4a#n200 This will affect any project using this code for migrations when using the mysql engine. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1301036/+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 1296333] Re: Keystone docs fail to build with SQLAlchemy 0.9
** Changed in: oslo Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1296333 Title: Keystone docs fail to build with SQLAlchemy 0.9 Status in OpenStack Identity (Keystone): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: When using SQLAlchemy 0.9, the docs fail to build. This is preventing Keystone from moving up to SQLAlchemy 0.9. There's a commit to update keystone's requirements to SQLAlchemy 0.9 which is failing the docs build: https://review.openstack.org/#/c/82231/ The log there only shows the first failure. When I generate docs on my build system I get the following errors: sphinx.errors.SphinxWarning: /opt/stack/keystone/keystone/common/sql/__init__.py:docstring of keystone.common.sql.relationship:53: ERROR: Unknown interpreted text role paramref. sphinx.errors.SphinxWarning: /opt/stack/keystone/keystone/openstack/common/db/sqlalchemy/utils.py: docstring of keystone.openstack.common.db.sqlalchemy.utils.or_:26: WARNING: more than one target found for cross-reference u'and_': keystone.common.sql.core.and_, keystone.common.sql.and_ sphinx.errors.SphinxWarning: /opt/stack/keystone/keystone/openstack/common/db/sqlalchemy/utils.py: docstring of keystone.openstack.common.db.sqlalchemy.utils.select:12: WARNING: undefined label: coretutorial_selecting (if the link has no caption the label must precede a section header) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1296333/+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 1292284] Re: A few tests from test_sqlalchemy_utils fail on SQLAlchemy 0.9.x
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = icehouse-rc1 -- 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/1292284 Title: A few tests from test_sqlalchemy_utils fail on SQLAlchemy 0.9.x Status in OpenStack Compute (Nova): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: When SQLAlchemy 0.9.x releases are used, some tests from test_sqlalchemy_utils module fail on assertRaises(). This is caused by the fact that we except SQLAlchemy to raise exceptions when reflecting SQLite custom data types from existing DB schema. This was true for SA 0.7.x and 0.8.x branches, but is fixed in 0.9.x releases. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1292284/+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 1289696] Re: request_id middleware uses wrong request ID value
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = icehouse-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1289696 Title: request_id middleware uses wrong request ID value Status in Cinder: Fix Committed Status in OpenStack Neutron (virtual network service): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: The request_id middleware is designed to generate a request ID during process_request() and attach this value to the as an HTTP header during process_response(). Unfortunately, it stores the request ID value in a variable within the RequestIdMiddleware class. This violates the shared nothing rule, and can cause problems when several requests are run concurrently. For example, if requests A and B come in back-to-back, and A completes first, A will have B's request ID value in the HTTP response. This problem was discovered when running nova's api.compute.servers.test_instance_actions test in parallel while working on https://review.openstack.org/#/c/66903/ To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1289696/+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 1288188] Re: unwanted lbaas related error logs in q-svc screen
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = icehouse-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1288188 Title: unwanted lbaas related error logs in q-svc screen Status in OpenStack Neutron (virtual network service): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: 2014-03-03 09:25:31.621 5910 ERROR root [-] Original exception being dropped: ['Traceback (most recent call last):\n', ' File /opt/stack/new/neutron/neutron/db/loadbalancer/loadbalancer_db.py, line 206, in _get_resource\nr = self._get_by_id(context, model, id)\n', ' File /opt/stack/new/neutron/neutron/db/db_base_plugin_v2.py, line 144, in _get_by_id\nreturn query.filter(model.id == id).one()\n', ' File /usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py, line 2323, in one\nraise orm_exc.NoResultFound(No row was found for one())\n', 'NoResultFound: No row was found for one()\n'] 2014-03-03 09:25:31.622 5910 WARNING neutron.services.loadbalancer.drivers.common.agent_driver_base [req-6949f3b4-f991-48b7-8424-b3bfbca7c822 None] Cannot update status: member d439c879-55f7-400f-b6a8-32753f057b05 not found in the DB, it was probably deleted concurrently There is no need for error log about original exception being dropped as warning log is enough. This happens due to using save_and_reraise_exception() in loadbalancer_db code: def _get_resource(self, context, model, id): try: r = self._get_by_id(context, model, id) except exc.NoResultFound: with excutils.save_and_reraise_exception(): if issubclass(model, Vip): raise loadbalancer.VipNotFound(vip_id=id) elif issubclass(model, Pool): raise loadbalancer.PoolNotFound(pool_id=id) elif issubclass(model, Member): raise loadbalancer.MemberNotFound(member_id=id) elif issubclass(model, HealthMonitor): raise loadbalancer.HealthMonitorNotFound(monitor_id=id) return r where the whole purpose of exception handler is to reraise proper type of exception. I think save_and_reraise_exception() was designed for cases when new exceptions raised inside exception handler are not expected. In this particular case I don't see the reason for using save_and_reraise_exception(). As an option I think a parameter can be added to save_and_reraise_exception() constructor to disable logging. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1288188/+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 1288049] Re: Lazy translation fails for complex formatting
** Changed in: oslo 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/1288049 Title: Lazy translation fails for complex formatting Status in OpenStack Compute (Nova): Confirmed Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: When lazy translation is enabled _() returns a gettextutils.Message instance. When formatting (%) is called on the instance rather than apply the replacement values, it gathers them so they can be applied when the message is lazily translated. This support includes the use of keyword replacement as part of formatting (passing a dictionary). In order to limit the size of the dictionary, especially in the case where locales is passed, the dictionary of values is limited to only those keywords that are actually referenced in the format string. The code that extracts the replacement keys (and thus dictionary entries to keep) only handles simple formatting. Currently it does not handle things like '%(key).02f', but instead omits them from the dictionary, which causes a KeyError when the message is translated and the replacements applied. Confirmed that regex that extracts the keywords does not handle this case: https://github.com/openstack/oslo-incubator/blob/master/openstack/common/gettextutils.py#L266 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1288049/+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 1281148] Re: QPID reconnection delay can't be configured
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = icehouse-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1281148 Title: QPID reconnection delay can't be configured Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Ceilometer havana series: Fix Released Status in Cinder: Invalid Status in Cinder havana series: Fix Released Status in OpenStack Identity (Keystone): Invalid Status in Keystone havana series: Fix Released Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron havana series: Fix Released Status in OpenStack Compute (Nova): Invalid Status in OpenStack Compute (nova) havana series: Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in oslo havana series: Fix Committed Status in Messaging API for OpenStack: Fix Released Bug description: Current qpid's reconnection can get up to 60s and it's not configurable. This is unfortunate because 60s is quite a lot of time to wait for HA systems, which makes this issue a blocker for this kind of deployments. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1281148/+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 1279000] Re: db migrate script to set charset=utf8 for all tables
** Changed in: oslo Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1279000 Title: db migrate script to set charset=utf8 for all tables Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in “glance” package in Ubuntu: Triaged Status in “glance” source package in Trusty: Triaged Bug description: 2014-02-11 17:42:15.495 26564 CRITICAL glance [-] ValueError: Tables image_locations,image_members,image_properties,image_tags,images,migrate_version,task_info,tasks have non utf8 collation, please make sure all tables are CHARSET=utf8 2014-02-11 17:42:15.495 26564 TRACE glance Traceback (most recent call last): 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv//bin/glance-manage, line 13, in module 2014-02-11 17:42:15.495 26564 TRACE glance sys.exit(main()) 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv/lib/python2.6/site-packages/glance/cmd/manage.py, line 220, in main 2014-02-11 17:42:15.495 26564 TRACE glance return CONF.command.action_fn() 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv/lib/python2.6/site-packages/glance/cmd/manage.py, line 121, in sync 2014-02-11 17:42:15.495 26564 TRACE glance CONF.command.current_version) 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv/lib/python2.6/site-packages/glance/cmd/manage.py, line 98, in sync 2014-02-11 17:42:15.495 26564 TRACE glance migration.db_sync(db_migration.MIGRATE_REPO_PATH, version) 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv/lib/python2.6/site-packages/glance/openstack/common/db/sqlalchemy/migration.py, line 195, in db_sync 2014-02-11 17:42:15.495 26564 TRACE glance _db_schema_sanity_check() 2014-02-11 17:42:15.495 26564 TRACE glance File /usr/local/csi/share/csi-glance.venv/lib/python2.6/site-packages/glance/openstack/common/db/sqlalchemy/migration.py, line 216, in _db_schema_sanity_check 2014-02-11 17:42:15.495 26564 TRACE glance ) % ','.join(table_names)) 2014-02-11 17:42:15.495 26564 TRACE glance ValueError: Tables image_locations,image_members,image_properties,image_tags,images,migrate_version,task_info,tasks have non utf8 collation, please make sure all tables are CHARSET=utf8 2014-02-11 17:42:15.495 26564 TRACE glance glance-manage fail to come up with above error. It's like due to following commit in oslo wherein we enforce charset=utf8 for all tables. 7aa94df Add a db check for CHARSET=utf8 I think we should have a migration script to change the charset for all tables. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1279000/+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 1288877] Re: Missing copyright text in oslo-incubator in openstack/common/__init__.py
** Changed in: oslo Status: Fix Committed = Fix Released ** Changed in: oslo Milestone: None = icehouse-rc1 -- 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/1288877 Title: Missing copyright text in oslo-incubator in openstack/common/__init__.py Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in OpenStack Compute (Nova): Invalid Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: The copyright text is missing from openstack/common/__init__.py in oslo-incubator and there is a missing line between the import and the following code line too. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1288877/+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 1302569] [NEW] 500 error in tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_integration_1
Public bug reported:
2014-04-03 16:41:43.208 | Traceback (most recent call last):
2014-04-03 16:41:43.208 | File
tempest/thirdparty/boto/test_ec2_instance_run.py, line 310, in
test_integration_1
2014-04-03 16:41:43.208 | volume.detach()
2014-04-03 16:41:43.208 | File
/usr/local/lib/python2.7/dist-packages/boto/ec2/volume.py, line 183, in detach
2014-04-03 16:41:43.208 | dry_run=dry_run
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py, line 2357, in
detach_volume
2014-04-03 16:41:43.209 | return self.get_status('DetachVolume', params,
verb='POST')
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1182, in
get_status
2014-04-03 16:41:43.209 | response = self.make_request(action, params,
path, verb)
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1089, in
make_request
2014-04-03 16:41:43.209 | return self._mexe(http_request)
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1002, in _mexe
2014-04-03 16:41:43.209 | raise BotoServerError(response.status,
response.reason, body)
2014-04-03 16:41:43.209 | BotoServerError: BotoServerError: 500 Internal Server
Error
2014-04-03 16:41:43.209 | ?xml version=1.0?
2014-04-03 16:41:43.209 |
ResponseErrorsErrorCodeKeyError/CodeMessageUnknown error
occurred./Message/Error/ErrorsRequestIDreq-57e4c659-2063-4598-a2ee-a0e961c8470e/RequestID/Response
http://logs.openstack.org/16/85016/2/check/check-grenade-
dsvm/5fba86f/console.html
http://logs.openstack.org/16/85016/2/check/check-grenade-
dsvm/5fba86f/logs/testr_results.html.gz
** 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/1302569
Title:
500 error in
tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_integration_1
Status in OpenStack Compute (Nova):
New
Bug description:
2014-04-03 16:41:43.208 | Traceback (most recent call last):
2014-04-03 16:41:43.208 | File
tempest/thirdparty/boto/test_ec2_instance_run.py, line 310, in
test_integration_1
2014-04-03 16:41:43.208 | volume.detach()
2014-04-03 16:41:43.208 | File
/usr/local/lib/python2.7/dist-packages/boto/ec2/volume.py, line 183, in detach
2014-04-03 16:41:43.208 | dry_run=dry_run
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py, line 2357, in
detach_volume
2014-04-03 16:41:43.209 | return self.get_status('DetachVolume', params,
verb='POST')
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1182, in
get_status
2014-04-03 16:41:43.209 | response = self.make_request(action, params,
path, verb)
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1089, in
make_request
2014-04-03 16:41:43.209 | return self._mexe(http_request)
2014-04-03 16:41:43.209 | File
/usr/local/lib/python2.7/dist-packages/boto/connection.py, line 1002, in _mexe
2014-04-03 16:41:43.209 | raise BotoServerError(response.status,
response.reason, body)
2014-04-03 16:41:43.209 | BotoServerError: BotoServerError: 500 Internal
Server Error
2014-04-03 16:41:43.209 | ?xml version=1.0?
2014-04-03 16:41:43.209 |
ResponseErrorsErrorCodeKeyError/CodeMessageUnknown error
occurred./Message/Error/ErrorsRequestIDreq-57e4c659-2063-4598-a2ee-a0e961c8470e/RequestID/Response
http://logs.openstack.org/16/85016/2/check/check-grenade-
dsvm/5fba86f/console.html
http://logs.openstack.org/16/85016/2/check/check-grenade-
dsvm/5fba86f/logs/testr_results.html.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1302569/+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 1245247] Re: For ldap, API wrongly reports user is in group
Reviewed: https://review.openstack.org/85103
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=628f383fbb14ae99679957ab05a02562a4d43d91
Submitter: Jenkins
Branch:milestone-proposed
commit 628f383fbb14ae99679957ab05a02562a4d43d91
Author: wanghong w.wangh...@huawei.com
Date: Mon Mar 17 17:22:08 2014 +0800
For ldap, API wrongly reports user is in group
When the ldap identity backend is configured,
HEAD v3/groups/{group_id}/users/{user_id}
always returns 200, even if the user is not actually in the group.
This is because the sql and kvs backend will raise NotFound
exception if the user is not in the group, but the ldap backend
just return result.
Change-Id: Ie1585c8aebe054091bd76fded666bf41125ff9ca
Closes-Bug: 1245247
** Changed in: keystone
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1245247
Title:
For ldap, API wrongly reports user is in group
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
When the ldap identity backend is configured,
HEAD v3/groups/{group_id}/users/{user_id}
always returns 200, regardless of whether or not the user is actually in the
group.
Fix is simple:
keystone.identity.backends.ldap.check_user_in_group() should raise an
exception if the user isn't in the group, rather than just return false
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1245247/+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 1302611] [NEW] policy.init called too many time for each API request
Public bug reported: policy.init() checks whether the rule cache is populated and valid, and if not reloads the policy cache from the policy.json file. As the current code runs init() each time a policy is checked or enforced, list operations will call init() several times (*) If policy.json is updated while a response is being generated, this will lead to a situation where some item are processed according to the old policies, and other according to the new ones, which would be wrong. Also, init() checks the last update time of the policy file, and repeating this check multiple time is wasteful. A simple solution would be to explicitly call policy.init from api.v2.base.Controller in order to ensure the method is called only once per API request. (*) a GET /ports operation returning 1600 ports calls policy.init() 9606 times ** Affects: neutron Importance: Medium Assignee: Salvatore Orlando (salvatore-orlando) Status: In Progress ** Tags: api havana-backport-potential icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302611 Title: policy.init called too many time for each API request Status in OpenStack Neutron (virtual network service): In Progress Bug description: policy.init() checks whether the rule cache is populated and valid, and if not reloads the policy cache from the policy.json file. As the current code runs init() each time a policy is checked or enforced, list operations will call init() several times (*) If policy.json is updated while a response is being generated, this will lead to a situation where some item are processed according to the old policies, and other according to the new ones, which would be wrong. Also, init() checks the last update time of the policy file, and repeating this check multiple time is wasteful. A simple solution would be to explicitly call policy.init from api.v2.base.Controller in order to ensure the method is called only once per API request. (*) a GET /ports operation returning 1600 ports calls policy.init() 9606 times To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302611/+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 1294603] Re: scenario test_load_balancer_basic fails
Reviewed: https://review.openstack.org/82480
Committed:
https://git.openstack.org/cgit/openstack/tempest/commit/?id=55d1314dde67ddafbb699d618bfba74bf6ad7714
Submitter: Jenkins
Branch:master
commit 55d1314dde67ddafbb699d618bfba74bf6ad7714
Author: Eugene Nikanorov enikano...@mirantis.com
Date: Mon Mar 24 15:39:21 2014 +0400
Unskip load balancer basic scenario test
Corresponding bug 1294603 was fixed by commit
I0dc4d01b0c1c04887ec6ad5766ec7c6c96903faa
Due to recent changes in neutron and nova which
fixed security groups for ml2 plugin
If004db60e084f4cea095ca9ecccb0537240d4183 and
I3bbcfc67036ab7389c82720add0bc0fc627bfee0,
one should create security group rules to allow traffic on specific tcp
port.
So patch adds rules to allow ingress traffic
for ports 80 and 88.
Closes-Bug: #1294603
Change-Id: Idff6d27611adda502e6e3f7e0d37f3acbda41d03
** Changed in: tempest
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/1294603
Title:
scenario test_load_balancer_basic fails
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in Tempest:
Fix Released
Bug description:
http://logs.openstack.org/98/81098/2/check/check-tempest-dsvm-neutron-
pg/df24b97/console.html
2014-03-19 09:58:15.379 | Traceback (most recent call last):
2014-03-19 09:58:15.379 | File tempest/test.py, line 121, in wrapper
2014-03-19 09:58:15.379 | return f(self, *func_args, **func_kwargs)
2014-03-19 09:58:15.379 | File
tempest/scenario/test_load_balancer_basic.py, line 225, in
test_load_balancer_basic
2014-03-19 09:58:15.379 | self._check_load_balancing()
2014-03-19 09:58:15.379 | File
tempest/scenario/test_load_balancer_basic.py, line 213, in
_check_load_balancing
2014-03-19 09:58:15.379 | http://{0}/.format(self.vip_ip)).read())
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/urllib.py, line 86, in
urlopen
2014-03-19 09:58:15.380 | return opener.open(url)
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/urllib.py, line 207, in
open
2014-03-19 09:58:15.380 | return getattr(self, name)(url)
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/urllib.py, line 345, in
open_http
2014-03-19 09:58:15.380 | errcode, errmsg, headers = h.getreply()
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/httplib.py, line 1102,
in getreply
2014-03-19 09:58:15.380 | response = self._conn.getresponse()
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/httplib.py, line 1030,
in getresponse
2014-03-19 09:58:15.380 | response.begin()
2014-03-19 09:58:15.380 | File /usr/lib/python2.7/httplib.py, line 407,
in begin
2014-03-19 09:58:15.381 | version, status, reason = self._read_status()
2014-03-19 09:58:15.381 | File /usr/lib/python2.7/httplib.py, line 365,
in _read_status
2014-03-19 09:58:15.381 | line = self.fp.readline()
2014-03-19 09:58:15.381 | File /usr/lib/python2.7/socket.py, line 430, in
readline
2014-03-19 09:58:15.381 | data = recv(1)
2014-03-19 09:58:15.381 | IOError: [Errno socket error] [Errno 104]
Connection reset by peer
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1294603/+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 1301982] Re: anti-affinity server boot failure shows stack trace
** Also affects: horizon 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/1301982 Title: anti-affinity server boot failure shows stack trace Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (Nova): In Progress Bug description: If anti-affinity policy is set for two different servers, and only one host is available, a stack trace is shown instead of a error message. Failure is expected, but a message about why it failed would be helpful. On a single node devstack setup: nova server-group-create --policy anti-affinity aagroup nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net- id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3 -423d-a9f4-41ac5d0fff07 server1 nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net- id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3 -423d-a9f4-41ac5d0fff07 server2 server1 boots fine server2 has Status Error and Power State No State Horizon shows: Fault Message unsupported operand type(s) for |: 'list' and 'set' Code 500 Details File /opt/stack/nova/nova/scheduler/manager.py, line 140, in run_instance legacy_bdm_in_spec) File /opt/stack/nova/nova/scheduler/filter_scheduler.py, line 86, in schedule_run_instance filter_properties, instance_uuids) File /opt/stack/nova/nova/scheduler/filter_scheduler.py, line 289, in _schedule filter_properties) File /opt/stack/nova/nova/scheduler/filter_scheduler.py, line 275, in _setup_instance_group filter_properties['group_hosts'] = user_hosts | group_hosts Created April 3, 2014, 1:58 p.m. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1301982/+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 1301935] Re: Dashboard ignores the HORIZON_CONFIG['user_home'] setting
Reviewed: https://review.openstack.org/85259 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=57bc46bfceb258e6a9fa6a007d6920618eafa167 Submitter: Jenkins Branch:milestone-proposed commit 57bc46bfceb258e6a9fa6a007d6920618eafa167 Author: Radomir Dopieralski openst...@sheep.art.pl Date: Thu Apr 3 14:05:42 2014 +0200 Don't ignore the HORIZON_CONFIG['user_home'] setting Dashboard has its own splash, with a hardcoded get_user_home that igonres HORIZON_CONFIG. This patch makes it use horiozn.get_user_home which actually checks the user_home setting, and with the default settings.py, uses dashboard's get_user_home anyways, but allows for changing that default behavior. Change-Id: Id2d957f0cd8fb8f2c053f0c5df4be177e18c Closes-bug: #1301935 (cherry picked from commit ef2f59f09dd9c27b202a65b38ccf77165f7363a4) ** Changed in: horizon Status: Fix Committed = 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/1301935 Title: Dashboard ignores the HORIZON_CONFIG['user_home'] setting Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Dashboard has its own splash, with a hardcoded get_user_home that igonres HORIZON_CONFIG. We need to make it use horiozn.get_user_home which actually checks the user_home setting, and with the default settings.py, uses dashboard's get_user_home anyways, but allows for changing that default behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1301935/+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 1275173] Re: _translate_from_glance() can cause an unnecessary HTTP request
Reviewed: https://review.openstack.org/85374
Committed:
https://git.openstack.org/cgit/openstack/cinder/commit/?id=01e5eac3f251164096051d43d763df72a65d31d3
Submitter: Jenkins
Branch:milestone-proposed
commit 01e5eac3f251164096051d43d763df72a65d31d3
Author: Chris Buccella bucce...@linux.vnet.ibm.com
Date: Thu Apr 3 04:02:45 2014 +
_translate_from_glance() can cause an unnecessary HTTP request
After returning from a get() call to python-glanceclient, cinder runs a
translation function on the returned Image to get the data it wants. Part of
this process is checking for an expected set of attributes, one of which is
the deletion time ('deleted_at'). However, if the image has not been
deleted,
deleted_at key will not exist. This forces another call to glance to occur
for
the same image. A similar problem exists for the checksum attribute, which
does
not exist before an image is active. The fix here is to only consider
deleted_at and checksum if they are expected to be present.
This change was made in nova as change I67b7dd16
Change-Id: Iedc16cb9316f9610fdb8ac03f448bc375a4e6bfa
Closes-Bug: #1275173
(cherry picked from commit da13c6285bb0aee55cfbc93f55ce2e2b7d6a28f2)
** Changed in: cinder
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/1275173
Title:
_translate_from_glance() can cause an unnecessary HTTP request
Status in Cinder:
Fix Released
Status in OpenStack Compute (Nova):
Fix Committed
Bug description:
I noticed when performing a nova image-show on a current (not
deleted) image, two HTTP requests were issued. Why isn't the Image
retrieved on the first GET request?
In fact, it is. The problem lies in _extract_attributes(), called by
_translate_from_glance(). This function loops through a list of
expected attributes, and extracts them from the passed-in Image. The
problem is that if the attribute 'deleted' is False, there won't be a
'deleted_at' attribute in the Image. Not finding the attribute results
in getattr() making another GET request (to try to find the missing
attribute?). This is unnecessary of course, since it makes sense for
the Image to not have that attribute set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1275173/+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 1302701] [NEW] Neutron refuses to delete instance associated with multiple floating addresses
Public bug reported: Neutron does not permit one to delete an instance that is associated with multiple floating ip addresses. Create an instance: nova boot ... --nic net-id=3ff9b903-e921-4752-a26f-cba8f1433992 --key- name lars test0 Add a second fixed ip address: nova add-fixed-ip test0 3ff9b903-e921-4752-a26f-cba8f1433992 nova show test0 | grep network | net0 network | 10.0.0.4, 10.0.0.5 | Associate a floating ip address with each fixed address: $ nova add-floating-ip --fixed-address 10.0.0.5 test0 192.168.200.7 $ nova add-floating-ip --fixed-address 10.0.0.4 test0 192.168.200.6 Now attempt to delete the instance: $ nova delete test0 $ nova list | grep test0 | c36e277f-e354-4856-8f5b-9603e6c76b2e | test0 | ERROR ... Neutron server fails with: ERROR neutron.api.v2.resource [-] delete failed TRACE neutron.api.v2.resource Traceback (most recent call last): TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py, line 84, in resource TRACE neutron.api.v2.resource result = method(request=request, **args) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/api/v2/base.py, line 432, in delete TRACE neutron.api.v2.resource obj_deleter(request.context, id, **kwargs) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/plugins/openvswitch/ovs_neutron_plugin.py, line 631, in delete_port TRACE neutron.api.v2.resource self.disassociate_floatingips(context, id) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/db/l3_db.py, line 751, in disassociate_floatingips TRACE neutron.api.v2.resource % port_id) TRACE neutron.api.v2.resource Exception: Multiple floating IPs found for port b591c76b-9d72-41d7-a884-2959a1f6b7fc TRACE neutron.api.v2.resource Disassociating one of the floating ips allows the delete to complete successfully: nova floating-ip-disassociate test0 192.168.200.6 nova delete test0 ** 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/1302701 Title: Neutron refuses to delete instance associated with multiple floating addresses Status in OpenStack Neutron (virtual network service): New Bug description: Neutron does not permit one to delete an instance that is associated with multiple floating ip addresses. Create an instance: nova boot ... --nic net-id=3ff9b903-e921-4752-a26f-cba8f1433992 --key-name lars test0 Add a second fixed ip address: nova add-fixed-ip test0 3ff9b903-e921-4752-a26f-cba8f1433992 nova show test0 | grep network | net0 network | 10.0.0.4, 10.0.0.5 | Associate a floating ip address with each fixed address: $ nova add-floating-ip --fixed-address 10.0.0.5 test0 192.168.200.7 $ nova add-floating-ip --fixed-address 10.0.0.4 test0 192.168.200.6 Now attempt to delete the instance: $ nova delete test0 $ nova list | grep test0 | c36e277f-e354-4856-8f5b-9603e6c76b2e | test0 | ERROR ... Neutron server fails with: ERROR neutron.api.v2.resource [-] delete failed TRACE neutron.api.v2.resource Traceback (most recent call last): TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/api/v2/resource.py, line 84, in resource TRACE neutron.api.v2.resource result = method(request=request, **args) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/api/v2/base.py, line 432, in delete TRACE neutron.api.v2.resource obj_deleter(request.context, id, **kwargs) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/plugins/openvswitch/ovs_neutron_plugin.py, line 631, in delete_port TRACE neutron.api.v2.resource self.disassociate_floatingips(context, id) TRACE neutron.api.v2.resource File /usr/lib/python2.7/site-packages/neutron/db/l3_db.py, line 751, in disassociate_floatingips TRACE neutron.api.v2.resource % port_id) TRACE neutron.api.v2.resource Exception: Multiple floating IPs found for port b591c76b-9d72-41d7-a884-2959a1f6b7fc TRACE neutron.api.v2.resource Disassociating one of the floating ips allows the delete to complete successfully: nova floating-ip-disassociate test0 192.168.200.6 nova delete test0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302701/+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 1301027] Re: Permission denied error in unit tests
Reviewed: https://review.openstack.org/84569 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ac2718c4aa7b6eb0c0e82df93cf59d890432d652 Submitter: Jenkins Branch:milestone-proposed commit ac2718c4aa7b6eb0c0e82df93cf59d890432d652 Author: Joe Gordon joe.gord...@gmail.com Date: Tue Apr 1 15:06:36 2014 -0700 Use a temp dir for CONF.state_path external_pids will defaults to $state_path(/var/lib/neutron)/external/pids which isn't accessible when running unit tests so use a tempdir for CONF.state_path. This bug arose when oslo.config 1.3.0 came out which fixed bug #1282250 (I4324bda6f3de3cdf05f8eb3cf16052c04018dec8) and caused this issue. Change-Id: I253c5ea85c51eff94399da0b9462d10a9c509a0f Closes-Bug: #1301027 ** Changed in: neutron Status: Fix Committed = 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/1301027 Title: Permission denied error in unit tests Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron havana series: Fix Released Bug description: Unit tests are intermittently failing because of permission denied errors on /var/lib/neutron It seems tmpdir fixtures are not being used. Logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiUGVybWlzc2lvbiBkZW5pZWQ6ICcvdmFyL2xpYi9uZXV0cm9uJ1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI0MzIwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTYzODY2NDIyNzB9 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301027/+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 938103] Re: don't set roles via metadata in backend api
Correct! This was fixed in https://review.openstack.org/#/c/71159/ ** Changed in: keystone Status: Confirmed = Invalid ** Changed in: keystone Assignee: Pablo Fernando Cargnelutti (pablo-fernando-cargnelutti) = Henry Nash (henry-nash) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/938103 Title: don't set roles via metadata in backend api Status in OpenStack Identity (Keystone): Invalid Bug description: In the testing code we use update_metadata to configure roles: self.metadata_foobar = self.identity_api.update_metadata( self.user_foo['id'], self.tenant_bar['id'], dict(roles=['keystone_admin'], is_admin='1')) I think that roles should be a separate (first order concept) from metadata When implementing a backend, you shouldn't have to examine the metadata to determine if you also need to update metadata. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/938103/+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 1298991] Re: Duplicated colon in _container_metadata.html
Reviewed: https://review.openstack.org/84204
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9c5c2d0291235826d3aa64ea4f16ff54b677cb2b
Submitter: Jenkins
Branch:milestone-proposed
commit 9c5c2d0291235826d3aa64ea4f16ff54b677cb2b
Author: Łukasz Jernaś deej...@srem.org
Date: Fri Mar 28 14:48:26 2014 +0100
Remove duplicate colon from Size string
Change-Id: I23354aae9427183bb79e4b51b2c8c29b3519e7ae
Closes-bug: #1298991
(cherry picked from commit e1f32355cd57b82d69ce78ca88af88e4a937316e)
** Changed in: horizon
Status: Fix Committed = 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/1298991
Title:
Duplicated colon in _container_metadata.html
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
There's a duplicated colon in _container_metadata.html
li{% trans Size: %}: {{
container.container_bytes_used|filesizeformat }}/li
As https://bugs.launchpad.net/horizon/+bug/1296075 will require more
work, I'm reporting it as a seperate issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1298991/+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 1302774] [NEW] Failed to detach volume because of volume not found error prevents vm teardown
Public bug reported: When running the boto tests in the gate we get a periodic race on Cinder volumes that can be seen as follows: Attach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_35_995 Detach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_41_477 Stack trace horribly because the volume is not found - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_43_866 Stack trace horribly because we try again? - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_42_29_353 Because of this we end up with a volume in an undeletable state, and the tests fail in making it go away (it remains marked in-use even though the guest that was using it is gone) - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/console.html#_2014-04-04_11_42_47_940 Logstash for these results is: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGlza05vdEZvdW5kOiBObyBkaXNrIGF0XCIgQU5EIHRhZ3M6c2NyZWVuLW4tY3B1LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NjYzNDM5MjIyOX0= ** Affects: cinder Importance: Undecided Status: New ** Affects: nova Importance: Undecided Status: New ** Affects: tempest Importance: Undecided Status: New ** Also affects: tempest 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/1302774 Title: Failed to detach volume because of volume not found error prevents vm teardown Status in Cinder: New Status in OpenStack Compute (Nova): New Status in Tempest: New Bug description: When running the boto tests in the gate we get a periodic race on Cinder volumes that can be seen as follows: Attach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_35_995 Detach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_41_477 Stack trace horribly because the volume is not found - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_43_866 Stack trace horribly because we try again? - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_42_29_353 Because of this we end up with a volume in an undeletable state, and the tests fail in making it go away (it remains marked in-use even though the guest that was using it is gone) - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/console.html#_2014-04-04_11_42_47_940 Logstash for these results is: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGlza05vdEZvdW5kOiBObyBkaXNrIGF0XCIgQU5EIHRhZ3M6c2NyZWVuLW4tY3B1LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NjYzNDM5MjIyOX0= To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1302774/+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 1302774] Re: Failed to detach volume because of volume not found error prevents vm teardown
Possibly a Tempest bug as well, as maybe there is a better tear down path here. ** Also affects: cinder 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/1302774 Title: Failed to detach volume because of volume not found error prevents vm teardown Status in Cinder: New Status in OpenStack Compute (Nova): New Status in Tempest: New Bug description: When running the boto tests in the gate we get a periodic race on Cinder volumes that can be seen as follows: Attach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_35_995 Detach the volume (vdh) - http://logs.openstack.org/29/84829/6/check /check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_41_477 Stack trace horribly because the volume is not found - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_43_866 Stack trace horribly because we try again? - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_42_29_353 Because of this we end up with a volume in an undeletable state, and the tests fail in making it go away (it remains marked in-use even though the guest that was using it is gone) - http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full- reexec/7e595ac/console.html#_2014-04-04_11_42_47_940 Logstash for these results is: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGlza05vdEZvdW5kOiBObyBkaXNrIGF0XCIgQU5EIHRhZ3M6c2NyZWVuLW4tY3B1LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NjYzNDM5MjIyOX0= To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1302774/+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 1287192] Re: Improve handle method on ManageAggregateHostWorkflow class
Reviewed: https://review.openstack.org/85263 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=09981bdb5a8675517f8c59578b0760ef1eb4a7eb Submitter: Jenkins Branch:milestone-proposed commit 09981bdb5a8675517f8c59578b0760ef1eb4a7eb Author: Alejandro Emanuel Paredes alejandro.e.pare...@intel.com Date: Mon Mar 10 18:14:07 2014 -0300 Improve Host Aggregates handle method. Added update conditions to the handle method (remove and add hosts). Previously, to perform an update, first all existing hosts were removed and then all new hosts were added. Now, the update method only remove or add the changed hosts. Added missing unit tests for the update. Change-Id: I52acdd1226be504cf2d0cf029353dbf80e4aa01a Closes-bug: #1287192 (cherry picked from commit 8f4331a6bdc12bb7632f2d170cc94176e0897fbf) ** Changed in: horizon Status: Fix Committed = 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/1287192 Title: Improve handle method on ManageAggregateHostWorkflow class Status in OpenStack Dashboard (Horizon): Fix Released Bug description: As it is said here: https://review.openstack.org/#/c/71061/12/openstack_dashboard/dashboards/admin/aggregates/workflows.py, the Workflows.py file contains the ManageAggregateHostWorkflow class. Inside it, the handle method should be improved (check the comments on the review). It will be ready to fix when the bp https://blueprints.launchpad.net/horizon/+spec/manage-host-aggregates was finished. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1287192/+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 1302791] [NEW] PLUMgrid CI Testing
Public bug reported: This is just a dummy bug for a dummy changeset to test PLUMgrid CI for stablization. It will be removed when work is done. ** Affects: neutron Importance: Undecided Assignee: Fawad Khaliq (fawadkhaliq) Status: New ** Changed in: neutron Assignee: (unassigned) = Fawad Khaliq (fawadkhaliq) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302791 Title: PLUMgrid CI Testing Status in OpenStack Neutron (virtual network service): New Bug description: This is just a dummy bug for a dummy changeset to test PLUMgrid CI for stablization. It will be removed when work is done. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302791/+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 1302796] [NEW] nova-compute (icehouse) exits with a misleading error when libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
Public bug reported: In Havana, this was a valid setting: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver The nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver class has been removed in Icehouse; if nova-compute is run with this setting in nova.conf, the resulting error is... 2014-04-04 19:33:55.783 17413 TRACE nova.virt.driver ImportError: Class LibvirtDriver cannot be found (['Traceback (most recent call last):\n', ' File /usr/lib/python2.6/site- packages/nova/openstack/common/importutils.py, line 29, in import_class\nreturn getattr(sys.modules[mod_str], class_str)\n', AttributeError: 'module' object has no attribute 'LibvirtDriver'\n]) ...which is misleading, and will cause people to start looking at the setting of compute_driver. The error is caused by the libvirt driver attempting to import the vif class: vif_class = importutils.import_class(CONF.libvirt.vif_driver) If this configuration option was valid in Havana, then: (a) there should probably be a deprecation warning prior to it going away, and (b) the error message in icehouse should point at the actual problem rather than throwing a misleading exception. ** 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/1302796 Title: nova-compute (icehouse) exits with a misleading error when libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver Status in OpenStack Compute (Nova): New Bug description: In Havana, this was a valid setting: libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver The nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver class has been removed in Icehouse; if nova-compute is run with this setting in nova.conf, the resulting error is... 2014-04-04 19:33:55.783 17413 TRACE nova.virt.driver ImportError: Class LibvirtDriver cannot be found (['Traceback (most recent call last):\n', ' File /usr/lib/python2.6/site- packages/nova/openstack/common/importutils.py, line 29, in import_class\nreturn getattr(sys.modules[mod_str], class_str)\n', AttributeError: 'module' object has no attribute 'LibvirtDriver'\n]) ...which is misleading, and will cause people to start looking at the setting of compute_driver. The error is caused by the libvirt driver attempting to import the vif class: vif_class = importutils.import_class(CONF.libvirt.vif_driver) If this configuration option was valid in Havana, then: (a) there should probably be a deprecation warning prior to it going away, and (b) the error message in icehouse should point at the actual problem rather than throwing a misleading exception. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302796/+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 1299145] Re: Documentation Bug, BigSwitch should be Big Switch
** Tags removed: icehouse-backport-potential ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Changed in: neutron Milestone: None = juno-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1299145 Title: Documentation Bug, BigSwitch should be Big Switch Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: BigSwitch references should be changed to Big Switch. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1299145/+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 1297875] Re: some tests call called_once_with_args with no assert, those lines are ignored
** Changed in: neutron
Milestone: None = juno-1
** Also affects: neutron/icehouse
Importance: Undecided
Status: New
** Changed in: neutron/icehouse
Milestone: None = icehouse-rc2
** Tags removed: icehouse-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1297875
Title:
some tests call called_once_with_args with no assert, those lines
are ignored
Status in OpenStack Neutron (virtual network service):
Fix Committed
Status in neutron icehouse series:
New
Bug description:
A few tests use called_once_with_args instead of mock's
assert_called_once_with_args
without checking the result.
That means that we're not asserting for that to happen.
Those tests need to be fixed.
[majopela@f20-devstack neutron]$ grep .called_once_with * -R | grep -v
assert
neutron/tests/unit/test_dhcp_agent.py:
disable.called_once_with_args(network.id)
neutron/tests/unit/test_dhcp_agent.py:
uuid5.called_once_with(uuid.NAMESPACE_DNS, 'localhost')
neutron/tests/unit/test_post_mortem_debug.py:
mock_print_exception.called_once_with(*exc_info)
neutron/tests/unit/test_db_migration.py:
mock_open.write.called_once_with('a')
neutron/tests/unit/test_agent_netns_cleanup.py:
ovs_br_cls.called_once_with('br-int', conf.AGENT.root_helper)
neutron/tests/unit/test_metadata_agent.py:
self.eventlet.wsgi.server.called_once_with(
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1297875/+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 1295854] Re: NSX plugin does not support pagination
** Changed in: neutron Milestone: None = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1295854 Title: NSX plugin does not support pagination Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: This should be rectified. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1295854/+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 1294526] Re: floatingip's id should be used instead of floatingip itself
** Changed in: neutron Importance: Medium = High ** Changed in: neutron Milestone: None = icehouse-rc2 ** Tags removed: icehouse-backport-potential ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Changed in: neutron Milestone: icehouse-rc2 = juno-1 ** Changed in: neutron/icehouse 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/1294526 Title: floatingip's id should be used instead of floatingip itself Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: https://github.com/openstack/neutron/blob/master/neutron/agent/l3_agent.py#L476 this id should be used as hash key instead of floating ip itself To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1294526/+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 1295448] Re: Big Switch Restproxy unit test unnecessarily duplicates tests
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1295448 Title: Big Switch Restproxy unit test unnecessarily duplicates tests Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: The VIF type tests currently have separate classes that all extend the ports test class. This means in addition to testing the VIF changing logic, it's unnecessarily exercising a lot of code that is not impacted by the VIF type. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1295448/+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 1302007] Re: l3 agent uses method concatenating two constants
** Changed in: neutron Milestone: None = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302007 Title: l3 agent uses method concatenating two constants Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: In l3 agent is method ns_name() that concatenates constant NS_PREFIX with router.id that doesn't change during router's lifecycle. It's ineffective, namespace name can be an instance attribute. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302007/+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 1301105] Re: Second firewall creation returns 500
** Changed in: neutron Milestone: None = juno-1 ** Changed in: neutron Importance: Low = Medium ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301105 Title: Second firewall creation returns 500 Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: Second firewall creation returns 500. It is an expected behavior of firewall reference implementation and an internal server error should not be returned. It is some kind of quota error and 409 looks appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301105/+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 1300628] Re: BigSwitch ML2 driver uses portbindingsports table
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Tags removed: icehouse-backport-potential ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300628 Title: BigSwitch ML2 driver uses portbindingsports table Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: The Big Switch ML2 driver references the deprecated portbindings_db in the port location tracking code. This needs to be removed because it's resulting in the entire portbinding_db schema for one small function. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300628/+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 1112912] Re: get_firewall_required should use VIF parameter from neutron
Great--thanks Nachi! ** Information type changed from Public Security to Public ** No longer affects: ossa -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1112912 Title: get_firewall_required should use VIF parameter from neutron Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in Tempest: In Progress Bug description: This bug report is from the discussion of https://review.openstack.org/#/c/19126/17/nova/virt/libvirt/vif.py I'm going to file this as a bug for tracking issue The patch introduces get_firewall_required function. But the patch checks only conf file. This should use quantum VIF parameter. https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/ovs_quantum_plugin.py#L513 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1112912/+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 1302814] [NEW] nova notifications configuration takes tenant_id in config
Public bug reported: Since Icehouse, Neutron is able to send notifications to Nova API about some networking events. To make it working, you have to provide nova_admin_tenant_id in neutron.conf, which is painful for configuration management when deploying OpenStack in production. Like in all OpenStack projects, we should have a new parameter nova_admin_tenant_name without hitting Keystone API to ask for the real ID. ** Affects: neutron Importance: Undecided Assignee: Emilien Macchi (emilienm) Status: New ** Changed in: neutron Assignee: (unassigned) = Emilien Macchi (emilienm) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302814 Title: nova notifications configuration takes tenant_id in config Status in OpenStack Neutron (virtual network service): New Bug description: Since Icehouse, Neutron is able to send notifications to Nova API about some networking events. To make it working, you have to provide nova_admin_tenant_id in neutron.conf, which is painful for configuration management when deploying OpenStack in production. Like in all OpenStack projects, we should have a new parameter nova_admin_tenant_name without hitting Keystone API to ask for the real ID. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302814/+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 1236641] Re: LDAP Backend does not implement 'extras' dictionary
General direction is to avoid the proliferation of 'extras' in favor of explicitly supporting attributes exposed to the API. ** 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 Keystone. https://bugs.launchpad.net/bugs/1236641 Title: LDAP Backend does not implement 'extras' dictionary Status in OpenStack Identity (Keystone): Won't Fix Bug description: According to this link: http://docs.openstack.org/developer/keystone/architecture.html#data-model It appears that the LDAP backend should contain an 'extras' dict that functions similarly to that of the SQL backend. However, this does not appear to be the case. For example, with the SQL backend, users can create key/value pairs under the extras column of a project. With the LDAP backend there is no such functionality. Users need to be able to add custom metadata to projects in the same way that they can with the SQL backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1236641/+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 1302831] [NEW] hacking/flake8 skips most xenapi plugins
Public bug reported: It appears to be because the plugins themselves don't have a filename that ends in .py so they get skipped. Only the few files in there that end .py are being checked. ** 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/1302831 Title: hacking/flake8 skips most xenapi plugins Status in OpenStack Compute (Nova): New Bug description: It appears to be because the plugins themselves don't have a filename that ends in .py so they get skipped. Only the few files in there that end .py are being checked. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1302831/+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 1302838] [NEW] newly spawned agent isn't learned by neutron very quickly
Public bug reported: 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp Traceback (most recent call last): 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/openstack/common/rpc/amqp.py, line 438, in _process_data 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp **args) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/common/rpc.py, line 45, in dispatch 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp neutron_ctxt, version, method, namespace, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/openstack/common/rpc/dispatcher.py, line 172, in dispatch 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/dhcp_rpc_base.py, line 65, in get_active_networks_info 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp networks = self._get_active_networks(context, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/dhcp_rpc_base.py, line 45, in _get_active_networks 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp context, host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/agentschedulers_db.py, line 179, in list_active_networks_on_active_dhcp_agent 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp context, constants.AGENT_TYPE_DHCP, host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/agents_db.py, line 133, in _get_agent_by_type_and_host 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp host=host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp AgentNotFoundByTypeHost: Agent with agent_type=DHCP agent and host=arosen-desktop could not be found Eventually the agent will be learned by neutron-server and this will go away. ** 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/1302838 Title: newly spawned agent isn't learned by neutron very quickly Status in OpenStack Neutron (virtual network service): New Bug description: 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp Traceback (most recent call last): 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/openstack/common/rpc/amqp.py, line 438, in _process_data 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp **args) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/common/rpc.py, line 45, in dispatch 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp neutron_ctxt, version, method, namespace, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/openstack/common/rpc/dispatcher.py, line 172, in dispatch 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/dhcp_rpc_base.py, line 65, in get_active_networks_info 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp networks = self._get_active_networks(context, **kwargs) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/dhcp_rpc_base.py, line 45, in _get_active_networks 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp context, host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/agentschedulers_db.py, line 179, in list_active_networks_on_active_dhcp_agent 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp context, constants.AGENT_TYPE_DHCP, host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp File /opt/stack/neutron/neutron/db/agents_db.py, line 133, in _get_agent_by_type_and_host 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp host=host) 2014-04-04 13:37:34.168 TRACE neutron.openstack.common.rpc.amqp AgentNotFoundByTypeHost: Agent with agent_type=DHCP agent and host=arosen-desktop could not be found Eventually the agent will be learned by neutron-server and this will go away. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302838/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe :
[Yahoo-eng-team] [Bug 1298459] Re: db migration: some tables are not created for bigswitch plugin and bigswitch mech driver
** Changed in: neutron Importance: Low = Medium ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-rc-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1298459 Title: db migration: some tables are not created for bigswitch plugin and bigswitch mech driver Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: For bigswitch plugin, networkdhcpagentbindings and subnetroutes tables are not created by db migration. http://openstack-ci-gw.bigswitch.com/logs/refs-changes-96-40296-13/BSN_PLUGIN/logs/screen/screen-q-svc.log.gz FOr bigswitch ML2 mech driver, neutron_ml2.consistencyhashes is not created by db migration. http://openstack-ci-gw.bigswitch.com/logs/refs-changes-96-40296-13/BSN_ML2/logs/screen/screen-q-svc.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1298459/+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 1301093] Re: Fixing API command for Arista Mechanism Driver
** Changed in: neutron Milestone: None = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-rc-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301093 Title: Fixing API command for Arista Mechanism Driver Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: A minor change is made to the Arista API between ML2 Driver and the back-end. This bug addresses this change to align Icehouse release with Arista EOS releases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301093/+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 1300808] Re: Invalid version number '['3.13.0']' with Ubuntu trusty
** Changed in: neutron Milestone: None = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Tags removed: icehouse-rc-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300808 Title: Invalid version number '['3.13.0']' with Ubuntu trusty Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: Running latest devstack on Trusty Ubuntu, the Neutron agent fails to start with the following backtrace: 2014-04-01 13:49:54.227 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['uname', '-r'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.232 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['uname', '-r'] Exit code: 0 Stdout: '3.13.0-20-generic\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.233 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.348 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] Exit code: 0 Stdout: 'ovs-vsctl (Open vSwitch) 2.0.1\nCompiled Feb 23 2014 14:42:32\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.349 DEBUG neutron.agent.linux.ovs_lib [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Checking OVS version for VXLAN support installed klm version is None, installed Linux version is ['3.13.0'], installed user version is 2.0 from (pid=14900) check_ovs_vxlan_version /opt/stack/neutron/neutron/agent/linux/ovs_lib.py:541 2014-04-01 13:49:54.350 CRITICAL neutron [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron Traceback (most recent call last): 2014-04-01 13:49:54.350 TRACE neutron File /usr/local/bin/neutron-openvswitch-agent, line 10, in module 2014-04-01 13:49:54.350 TRACE neutron sys.exit(main()) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1360, in main 2014-04-01 13:49:54.350 TRACE neutron agent = OVSNeutronAgent(**agent_config) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 214, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self._check_ovs_version() 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 232, in _check_ovs_version 2014-04-01 13:49:54.350 TRACE neutron ovs_lib.check_ovs_vxlan_version(self.root_helper) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 550, in check_ovs_vxlan_version 2014-04-01 13:49:54.350 TRACE neutron 'kernel', 'VXLAN') 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 507, in _compare_installed_and_required_version 2014-04-01 13:49:54.350 TRACE neutron installed_kernel_version) = dist_version.StrictVersion( 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 40, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self.parse(vstring) 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 107, in parse 2014-04-01 13:49:54.350 TRACE neutron raise ValueError, invalid version number '%s' % vstring 2014-04-01 13:49:54.350 TRACE neutron ValueError: invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron q-agt failed to start This is due to bug #1291535 and this fix: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2f65d9d447ddf2caf3b9c754bd00a5148bdf12c To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300808/+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 1302304] Re: tox pep8 warns /bin/bash not installed in testenv
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Changed in: neutron/icehouse Importance: Undecided = High ** Tags removed: icehouse-rc-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302304 Title: tox pep8 warns /bin/bash not installed in testenv Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: New Bug description: $ tox -e pep8 pep8 develop-inst-nodeps: /home/henry/Dev/neutron pep8 runtests: commands[0] | flake8 pep8 runtests: commands[1] | neutron-db-manage check_migration pep8 runtests: commands[2] | bash -c find neutron -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null WARNING:test command found but not installed in testenv cmd: /bin/bash env: /home/henry/Dev/neutron/.tox/pep8 Maybe forgot to specify a dependency? This is due to the tox.ini changes in https://review.openstack.org/84234 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302304/+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 1236372] Re: Router without active ports fails to be deleted, are reports wrong error message
** Also affects: neutron/icehouse
Importance: Undecided
Status: New
** Changed in: neutron/icehouse
Milestone: None = icehouse-rc2
** Changed in: neutron/icehouse
Assignee: (unassigned) = Mark McClain (markmcclain)
** Changed in: neutron/icehouse
Importance: Undecided = Low
** Changed in: neutron/icehouse
Status: New = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1236372
Title:
Router without active ports fails to be deleted, are reports wrong
error message
Status in OpenStack Neutron (virtual network service):
Fix Committed
Status in neutron icehouse series:
In Progress
Bug description:
Version
===
Havana, RHEL, neutron+ovs, python-neutron-2013.2-0.3.3.b3.el6ost
Description
===
It's impossible to delete a router while it still has inactive ports.
The error message states that the router still has active ports.
# neutron router-port-list router1
+--+--+---+--+
| id | name | mac_address | fixed_ips
|
+--+--+---+--+
| 052a48e4-0868-4675-bef7-8f763dd697b4 | | fa:16:3e:60:73:8d |
{subnet_id: c5d63940-71e8-4338-865e-f5364fbe4e78, ip_address:
10.35.214.1} |
| 065cef02-a949-45c9-b3df-e005dbf96c9a | | fa:16:3e:a6:6d:d8 |
{subnet_id: 044bcc05-f37b-4d1d-a700-c91c4381fbc8, ip_address:
10.35.211.1} |
| 7a020243-90e5-439d-90fb-ec96b07843e7 | | fa:16:3e:04:0c:1f |
{subnet_id: 4081fbca-3e59-4be5-a98e-3c9e0d13d3a6, ip_address:
10.35.212.1} |
| 7af56958-674e-472b-8dbe-09b60501a6e6 | | fa:16:3e:1a:07:a4 |
{subnet_id: ef8e7c03-f17f-4c3c-9afe-252aca1283fd, ip_address:
10.35.170.102} |
| f034cb8a-2a09-4d41-b46c-a08fe208461e | | fa:16:3e:de:9d:32 |
{subnet_id: cca4edc7-2872-4c1e-a270-3b0beb60f421, ip_address:
10.35.213.1} |
+--+--+---+--+
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-update $i --admin_state_up False ; done | grep status
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
From /var/log/neutron/server.log
2013-10-07 16:39:40.429 2341 ERROR neutron.api.v2.resource [-] delete failed
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py, line 84, in
resource
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/base.py, line 432, in delete
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource
obj_deleter(request.context, id, **kwargs)
[Yahoo-eng-team] [Bug 1288582] Re: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron Milestone: icehouse-rc2 = juno-1 ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** Changed in: neutron/icehouse Assignee: (unassigned) = Mark McClain (markmcclain) ** Changed in: neutron/icehouse Importance: Undecided = Medium ** Changed in: neutron/icehouse Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1288582 Title: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: In Progress Bug description: Neutron assumes that all ports with the device_owner that start with 'compute' are ports created by nova compute. Thus, when the debug agent creates a port with device_owner = compute:probe the nova callback feature tells nova when this port is wired even though nova does not know about (doesn't really matter we just log an error). This patch just renames this device_owner to not start with compute to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1288582/+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 1245208] Re: LBaaS: unit tests for radware plugin driver should not employ multithreading
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Importance: Undecided = Medium ** Changed in: neutron/icehouse Assignee: (unassigned) = Mark McClain (markmcclain) ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1245208 Title: LBaaS: unit tests for radware plugin driver should not employ multithreading Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Radware plugin driver uses task queue to perform interaction with the backend device. Several operations such as lbaas objects deletion are performed in async manner. In the unit test code actual object deletion happens in separate thread; it leads to a need for tricks like putting test thread to sleep. Such unit tests are not reliable and could lead to failures that are hard to catch or debug. Unit test code should be refactored in such way that it uses single- threaded strategy to perform driver operations. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1245208/+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 1289139] Re: Configurable values is not printed in the OFA agent log file
** Changed in: neutron Milestone: icehouse-rc2 = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Status: New = In Progress ** Changed in: neutron/icehouse Importance: Undecided = Low ** Changed in: neutron/icehouse Assignee: (unassigned) = Mark McClain (markmcclain) ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1289139 Title: Configurable values is not printed in the OFA agent log file Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: In Progress Bug description: When the neutron-server starts up, it prints out the configurable values in the q-svc log. This values is useful in debugging problems. Such output is not in the OFA agent's log file. related bug 1285962 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1289139/+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 1291619] Re: Cisco VPN device drivers admin state not reported correctly
** Changed in: neutron Milestone: icehouse-rc2 = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Importance: Undecided = High ** Changed in: neutron/icehouse Status: New = In Progress ** Changed in: neutron/icehouse Assignee: (unassigned) = Mark McClain (markmcclain) ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291619 Title: Cisco VPN device drivers admin state not reported correctly Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: In Progress Bug description: Currently, this driver supports update of the VPN service, which one can change the admin state to up or down. In addition, even though IPSec site-to-site connection update is not currently supported (one can do a delete/create), the user could create the connection with admin state down. When the service admin state is changed to down, the change does not happen in the device driver, and the status is not reported correctly. This is due to an issue with the plugin (bug 1291609 created). If later, another change occurs that causes a sync of the config, the connections on the VPN service will be deleted (the CSR REST API doesn't yet have support for admin down), but the status still will not be updated correctly. The configuration in OpenStack can get out of sync with the configuration on the CSR. If the IPSec site-to-site connection is created in admin down state, the underlying tunnel is not created (correct), but the status still shows PENDING_CREATE. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1291619/+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 1291915] Re: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken
** Changed in: neutron Milestone: icehouse-rc2 = juno-1 ** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Status: New = In Progress ** Changed in: neutron/icehouse Importance: Undecided = High ** Changed in: neutron/icehouse Assignee: (unassigned) = Mark McClain (markmcclain) ** Changed in: neutron/icehouse Milestone: None = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291915 Title: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: In Progress Bug description: 1st) Some configuration options are not registered on the tool, but they're used in neutron.agent.linux.dhcp during execution $ neutron-netns-cleanup --debug --force --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini 2014-03-12 14:55:44.791 INFO neutron.common.config [-] Logging enabled! 2014-03-12 14:55:44.792 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] from (pid=1785) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-03-12 14:55:45.001 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] Exit code: 0 Stdout: 'qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2\nqrouter-acc5f724-a169-4ffc-9e81-f00d43954509\nqrouter-5ed23337-9538-4994-823f-c64720506e54\n' Stderr: '' from (pid=1785) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 14:55:47.006 ERROR neutron.agent.linux.dhcp [-] Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth 2nd) When we try to destroy a network, there's a dependency on the .namespace attribute of the network, that wasn't before. Stderr: '' from (pid=1969) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 15:08:53.048 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace: qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util Traceback (most recent call last): 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 131, in destroy_namespace 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util kill_dhcp(conf, namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 86, in kill_dhcp 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util dhcp_driver.disable() 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 181, in disable 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.device_manager.destroy(self.network, self.interface_name) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 814, in destroy 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.driver.unplug(device_name, namespace=network.namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util AttributeError: 'FakeNetwork' object has no attribute 'namespace' 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util 3rd) This error will happen because no plugin rpc connection is provided, and that's used in /opt/stack/neutron/neutron/agent/linux/dhcp.py as self.plugin.release_dhcp_port 2014-03-13 12:00:07.880 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace: qdhcp-388a37af-556d-4f4c-98b4-0ba41f944e32 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util Traceback (most recent call last): 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 132, in destroy_namespace 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util kill_dhcp(conf, namespace) 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 87, in kill_dhcp 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util dhcp_driver.disable() 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 181, in disable 2014-03-13 12:00:07.880 TRACE
[Yahoo-eng-team] [Bug 1301449] Re: ODL ML2 driver doesn't notify active/inactive ports
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301449 Title: ODL ML2 driver doesn't notify active/inactive ports Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: The nova-event-callback blueprint [1] implemented the notifications of active/down ports to Nova. Before effectively starting an instance, Nova compute waits for a VIF plugged notification from Neutron. I'm running ODL ML2 driver in a devstack using the master branch and I notice that the ODL driver doesn't notify back the Nova API. Hence with the default settings, the VM creation always fails. As a workaround, set the following parameters in your nova.conf: vif_plugging_timeout = 10 vif_plugging_is_fatal = False With this configuration, I'm able to boot and connect to the instances but the Neutron ports are always reported as DOWN [2]. [1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback [2] http://paste.openstack.org/show/74861/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301449/+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 1265498] Re: Router over quota error without tenant isolation
Reviewed: https://review.openstack.org/84904 Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=3e9d12b8af7a30a3d60297e4e53cf1a8626ab4c1 Submitter: Jenkins Branch:master commit 3e9d12b8af7a30a3d60297e4e53cf1a8626ab4c1 Author: Adam Gandelman ad...@ubuntu.com Date: Wed Apr 2 17:04:19 2014 -0700 Remove created routers as part of test cleanup The network API routers test currently creates a total of 10 routers (the default quota limit) but only deletes them in bulk during tearDownClass(). This can create issues hitting quota limits on setups without isolated credentials, or environments that may already have routers created outside of Tempest. This associates a cleanup with each created router and ensures each individual test deletes the routers it creates. Change-Id: I7f0e20cfe483fe3aa55d4641ca92ad9947fffbcc Closes-bug: #1265498 ** Changed in: tempest 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/1265498 Title: Router over quota error without tenant isolation Status in OpenStack Neutron (virtual network service): Invalid Status in Tempest: Fix Released Bug description: With parallel testing enabled, an error has been observed [1]. It seems the router quota is exceeded, which is compatible with a scenario where several tests creating routers are concurrently executed, and full tenant isolation is not enabled. There does not seem to be any issue on the neutron side; this error is probably due to tempest tests which needs to be made more robust - or perhaps it will just go away with full isolation [1] http://logs.openstack.org/85/64185/1/experimental/check-tempest- dsvm-neutron-isolated-parallel/706d454/console.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1265498/+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 1289139] Re: Configurable values is not printed in the OFA agent log file
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1289139 Title: Configurable values is not printed in the OFA agent log file Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: When the neutron-server starts up, it prints out the configurable values in the q-svc log. This values is useful in debugging problems. Such output is not in the OFA agent's log file. related bug 1285962 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1289139/+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 1236372] Re: Router without active ports fails to be deleted, are reports wrong error message
** Changed in: neutron
Milestone: juno-1 = icehouse-rc2
** No longer affects: neutron/icehouse
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1236372
Title:
Router without active ports fails to be deleted, are reports wrong
error message
Status in OpenStack Neutron (virtual network service):
Fix Committed
Bug description:
Version
===
Havana, RHEL, neutron+ovs, python-neutron-2013.2-0.3.3.b3.el6ost
Description
===
It's impossible to delete a router while it still has inactive ports.
The error message states that the router still has active ports.
# neutron router-port-list router1
+--+--+---+--+
| id | name | mac_address | fixed_ips
|
+--+--+---+--+
| 052a48e4-0868-4675-bef7-8f763dd697b4 | | fa:16:3e:60:73:8d |
{subnet_id: c5d63940-71e8-4338-865e-f5364fbe4e78, ip_address:
10.35.214.1} |
| 065cef02-a949-45c9-b3df-e005dbf96c9a | | fa:16:3e:a6:6d:d8 |
{subnet_id: 044bcc05-f37b-4d1d-a700-c91c4381fbc8, ip_address:
10.35.211.1} |
| 7a020243-90e5-439d-90fb-ec96b07843e7 | | fa:16:3e:04:0c:1f |
{subnet_id: 4081fbca-3e59-4be5-a98e-3c9e0d13d3a6, ip_address:
10.35.212.1} |
| 7af56958-674e-472b-8dbe-09b60501a6e6 | | fa:16:3e:1a:07:a4 |
{subnet_id: ef8e7c03-f17f-4c3c-9afe-252aca1283fd, ip_address:
10.35.170.102} |
| f034cb8a-2a09-4d41-b46c-a08fe208461e | | fa:16:3e:de:9d:32 |
{subnet_id: cca4edc7-2872-4c1e-a270-3b0beb60f421, ip_address:
10.35.213.1} |
+--+--+---+--+
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-update $i --admin_state_up False ; done | grep status
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
From /var/log/neutron/server.log
2013-10-07 16:39:40.429 2341 ERROR neutron.api.v2.resource [-] delete failed
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py, line 84, in
resource
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/base.py, line 432, in delete
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource
obj_deleter(request.context, id, **kwargs)
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/db/l3_db.py, line 266, in
delete_router
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource raise
l3.RouterInUse(router_id=id)
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource
[Yahoo-eng-team] [Bug 1301105] Re: Second firewall creation returns 500
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301105 Title: Second firewall creation returns 500 Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: Second firewall creation returns 500. It is an expected behavior of firewall reference implementation and an internal server error should not be returned. It is some kind of quota error and 409 looks appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301105/+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 1301093] Re: Fixing API command for Arista Mechanism Driver
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1301093 Title: Fixing API command for Arista Mechanism Driver Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: A minor change is made to the Arista API between ML2 Driver and the back-end. This bug addresses this change to align Icehouse release with Arista EOS releases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301093/+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 1288582] Re: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1288582 Title: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: Neutron assumes that all ports with the device_owner that start with 'compute' are ports created by nova compute. Thus, when the debug agent creates a port with device_owner = compute:probe the nova callback feature tells nova when this port is wired even though nova does not know about (doesn't really matter we just log an error). This patch just renames this device_owner to not start with compute to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1288582/+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 1291619] Re: Cisco VPN device drivers admin state not reported correctly
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291619 Title: Cisco VPN device drivers admin state not reported correctly Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: Currently, this driver supports update of the VPN service, which one can change the admin state to up or down. In addition, even though IPSec site-to-site connection update is not currently supported (one can do a delete/create), the user could create the connection with admin state down. When the service admin state is changed to down, the change does not happen in the device driver, and the status is not reported correctly. This is due to an issue with the plugin (bug 1291609 created). If later, another change occurs that causes a sync of the config, the connections on the VPN service will be deleted (the CSR REST API doesn't yet have support for admin down), but the status still will not be updated correctly. The configuration in OpenStack can get out of sync with the configuration on the CSR. If the IPSec site-to-site connection is created in admin down state, the underlying tunnel is not created (correct), but the status still shows PENDING_CREATE. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1291619/+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 1291915] Re: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291915 Title: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: 1st) Some configuration options are not registered on the tool, but they're used in neutron.agent.linux.dhcp during execution $ neutron-netns-cleanup --debug --force --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini 2014-03-12 14:55:44.791 INFO neutron.common.config [-] Logging enabled! 2014-03-12 14:55:44.792 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] from (pid=1785) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-03-12 14:55:45.001 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] Exit code: 0 Stdout: 'qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2\nqrouter-acc5f724-a169-4ffc-9e81-f00d43954509\nqrouter-5ed23337-9538-4994-823f-c64720506e54\n' Stderr: '' from (pid=1785) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 14:55:47.006 ERROR neutron.agent.linux.dhcp [-] Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth 2nd) When we try to destroy a network, there's a dependency on the .namespace attribute of the network, that wasn't before. Stderr: '' from (pid=1969) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 15:08:53.048 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace: qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util Traceback (most recent call last): 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 131, in destroy_namespace 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util kill_dhcp(conf, namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 86, in kill_dhcp 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util dhcp_driver.disable() 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 181, in disable 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.device_manager.destroy(self.network, self.interface_name) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 814, in destroy 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.driver.unplug(device_name, namespace=network.namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util AttributeError: 'FakeNetwork' object has no attribute 'namespace' 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util 3rd) This error will happen because no plugin rpc connection is provided, and that's used in /opt/stack/neutron/neutron/agent/linux/dhcp.py as self.plugin.release_dhcp_port 2014-03-13 12:00:07.880 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace: qdhcp-388a37af-556d-4f4c-98b4-0ba41f944e32 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util Traceback (most recent call last): 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 132, in destroy_namespace 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util kill_dhcp(conf, namespace) 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 87, in kill_dhcp 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util dhcp_driver.disable() 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 181, in disable 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util self.device_manager.destroy(self.network, self.interface_name) 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 816, in destroy 2014-03-13 12:00:07.880 TRACE neutron.agent.netns_cleanup_util self.plugin.release_dhcp_port(network.id, 2014-03-13 12:00:07.880
[Yahoo-eng-team] [Bug 1300628] Re: BigSwitch ML2 driver uses portbindingsports table
** No longer affects: neutron/icehouse ** Changed in: neutron Milestone: juno-1 = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300628 Title: BigSwitch ML2 driver uses portbindingsports table Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: The Big Switch ML2 driver references the deprecated portbindings_db in the port location tracking code. This needs to be removed because it's resulting in the entire portbinding_db schema for one small function. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300628/+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 1300808] Re: Invalid version number '['3.13.0']' with Ubuntu trusty
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1300808 Title: Invalid version number '['3.13.0']' with Ubuntu trusty Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: Running latest devstack on Trusty Ubuntu, the Neutron agent fails to start with the following backtrace: 2014-04-01 13:49:54.227 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['uname', '-r'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.232 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['uname', '-r'] Exit code: 0 Stdout: '3.13.0-20-generic\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.233 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.348 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] Exit code: 0 Stdout: 'ovs-vsctl (Open vSwitch) 2.0.1\nCompiled Feb 23 2014 14:42:32\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.349 DEBUG neutron.agent.linux.ovs_lib [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Checking OVS version for VXLAN support installed klm version is None, installed Linux version is ['3.13.0'], installed user version is 2.0 from (pid=14900) check_ovs_vxlan_version /opt/stack/neutron/neutron/agent/linux/ovs_lib.py:541 2014-04-01 13:49:54.350 CRITICAL neutron [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron Traceback (most recent call last): 2014-04-01 13:49:54.350 TRACE neutron File /usr/local/bin/neutron-openvswitch-agent, line 10, in module 2014-04-01 13:49:54.350 TRACE neutron sys.exit(main()) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1360, in main 2014-04-01 13:49:54.350 TRACE neutron agent = OVSNeutronAgent(**agent_config) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 214, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self._check_ovs_version() 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 232, in _check_ovs_version 2014-04-01 13:49:54.350 TRACE neutron ovs_lib.check_ovs_vxlan_version(self.root_helper) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 550, in check_ovs_vxlan_version 2014-04-01 13:49:54.350 TRACE neutron 'kernel', 'VXLAN') 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 507, in _compare_installed_and_required_version 2014-04-01 13:49:54.350 TRACE neutron installed_kernel_version) = dist_version.StrictVersion( 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 40, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self.parse(vstring) 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 107, in parse 2014-04-01 13:49:54.350 TRACE neutron raise ValueError, invalid version number '%s' % vstring 2014-04-01 13:49:54.350 TRACE neutron ValueError: invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron q-agt failed to start This is due to bug #1291535 and this fix: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2f65d9d447ddf2caf3b9c754bd00a5148bdf12c To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300808/+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 1298459] Re: db migration: some tables are not created for bigswitch plugin and bigswitch mech driver
** No longer affects: neutron/icehouse ** Changed in: neutron Milestone: juno-1 = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1298459 Title: db migration: some tables are not created for bigswitch plugin and bigswitch mech driver Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: For bigswitch plugin, networkdhcpagentbindings and subnetroutes tables are not created by db migration. http://openstack-ci-gw.bigswitch.com/logs/refs-changes-96-40296-13/BSN_PLUGIN/logs/screen/screen-q-svc.log.gz FOr bigswitch ML2 mech driver, neutron_ml2.consistencyhashes is not created by db migration. http://openstack-ci-gw.bigswitch.com/logs/refs-changes-96-40296-13/BSN_ML2/logs/screen/screen-q-svc.log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1298459/+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 1299145] Re: Documentation Bug, BigSwitch should be Big Switch
** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1299145 Title: Documentation Bug, BigSwitch should be Big Switch Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: BigSwitch references should be changed to Big Switch. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1299145/+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 1297875] Re: some tests call called_once_with_args with no assert, those lines are ignored
** No longer affects: neutron/icehouse
** Changed in: neutron
Milestone: juno-1 = icehouse-rc2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1297875
Title:
some tests call called_once_with_args with no assert, those lines
are ignored
Status in OpenStack Neutron (virtual network service):
Fix Committed
Bug description:
A few tests use called_once_with_args instead of mock's
assert_called_once_with_args
without checking the result.
That means that we're not asserting for that to happen.
Those tests need to be fixed.
[majopela@f20-devstack neutron]$ grep .called_once_with * -R | grep -v
assert
neutron/tests/unit/test_dhcp_agent.py:
disable.called_once_with_args(network.id)
neutron/tests/unit/test_dhcp_agent.py:
uuid5.called_once_with(uuid.NAMESPACE_DNS, 'localhost')
neutron/tests/unit/test_post_mortem_debug.py:
mock_print_exception.called_once_with(*exc_info)
neutron/tests/unit/test_db_migration.py:
mock_open.write.called_once_with('a')
neutron/tests/unit/test_agent_netns_cleanup.py:
ovs_br_cls.called_once_with('br-int', conf.AGENT.root_helper)
neutron/tests/unit/test_metadata_agent.py:
self.eventlet.wsgi.server.called_once_with(
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1297875/+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 1295854] Re: NSX plugin does not support pagination
** No longer affects: neutron/icehouse ** Changed in: neutron Milestone: juno-1 = icehouse-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1295854 Title: NSX plugin does not support pagination Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: This should be rectified. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1295854/+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 1295448] Re: Big Switch Restproxy unit test unnecessarily duplicates tests
** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1295448 Title: Big Switch Restproxy unit test unnecessarily duplicates tests Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: The VIF type tests currently have separate classes that all extend the ports test class. This means in addition to testing the VIF changing logic, it's unnecessarily exercising a lot of code that is not impacted by the VIF type. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1295448/+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 1302304] Re: tox pep8 warns /bin/bash not installed in testenv
** No longer affects: neutron/icehouse ** Tags added: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302304 Title: tox pep8 warns /bin/bash not installed in testenv Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: $ tox -e pep8 pep8 develop-inst-nodeps: /home/henry/Dev/neutron pep8 runtests: commands[0] | flake8 pep8 runtests: commands[1] | neutron-db-manage check_migration pep8 runtests: commands[2] | bash -c find neutron -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null WARNING:test command found but not installed in testenv cmd: /bin/bash env: /home/henry/Dev/neutron/.tox/pep8 Maybe forgot to specify a dependency? This is due to the tox.ini changes in https://review.openstack.org/84234 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302304/+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 1294526] Re: floatingip's id should be used instead of floatingip itself
** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1294526 Title: floatingip's id should be used instead of floatingip itself Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: https://github.com/openstack/neutron/blob/master/neutron/agent/l3_agent.py#L476 this id should be used as hash key instead of floating ip itself To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1294526/+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 1302007] Re: l3 agent uses method concatenating two constants
** Changed in: neutron Milestone: juno-1 = icehouse-rc2 ** No longer affects: neutron/icehouse -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302007 Title: l3 agent uses method concatenating two constants Status in OpenStack Neutron (virtual network service): Fix Committed Bug description: In l3 agent is method ns_name() that concatenates constant NS_PREFIX with router.id that doesn't change during router's lifecycle. It's ineffective, namespace name can be an instance attribute. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302007/+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 1302889] [NEW] Rescheduling causes PortInUse failure
Public bug reported: I have a 10 compute nodes OpenStack Icehouse 3 environment. One of these compute nodes was incorrectly configured with permission issue on /var/lib/nova/instance (as it was mounted on SAN storage device). When the instance was schedule to run on this suspect compute node, it failed and got re-scheduled to another node. The launch failed on that node too, but the failure was due to PortInUse. Scheduler relaunched on the 3rd node, and there too it failed with PortInUse error. It looks like re-scheduling does not work on all the cases. Expected behavior: Anyone of the following: 1. Don't reschedule an instance in such error condition. 2. If scheduled the port being created in the first launch must be de-coupled or detached. nova-scheduler.log.1:2014-04-04 04:55:20.647 17861 INFO nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] Attempting to build 1 instance(s) uuids: [u'7b66bc37-cd0a-476a-a0a9-c06b84a9d31a'] nova-scheduler.log.1:2014-04-04 04:55:20.658 17861 INFO nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] Choosing host WeighedHost [host: i3computebay7, weight: 1.0] for instance 7b66bc37-cd0a-476a-a0a9-c06b84a9d31a nova-scheduler.log.1:2014-04-04 04:55:22.899 17861 INFO nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] Attempting to build 1 instance(s) uuids: [u'7b66bc37-cd0a-476a-a0a9-c06b84a9d31a'] nova-scheduler.log.1:2014-04-04 04:55:22.901 17861 ERROR nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] [instance: 7b66bc37-cd0a-476a-a0a9-c06b84a9d31a] Error from last host: i3computebay7 (node i3computebay7.cdl.local): [u'Traceback (most recent call last):\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1065, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 360, in decorated_function\nreturn function(self, context, *args, **kwargs)\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1475, in _spawn\nLOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py, line 68, in __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u' File /usr/lib/python2. 7/dist-packages/nova/compute/manager.py, line 1472, in _spawn\n block_device_info)\n', u' File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2230, in spawn\nadmin_pass=admin_password)\n', u' File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 2478, in _create_image\n fileutils.ensure_tree(libvirt_utils.get_instance_path(instance))\n', u' File /usr/lib/python2.7/dist-packages/nova/openstack/common/fileutils.py, line 37, in ensure_tree\nos.makedirs(path)\n', u' File /usr/lib/python2.7/os.py, line 157, in makedirs\nmkdir(name, mode)\n', uOSError: [Errno 13] Permission denied: '/var/lib/nova/instances/7b66bc37-cd0a-476a-a0a9-c06b84a9d31a'\n] nova-scheduler.log.1:2014-04-04 04:55:22.913 17861 INFO nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] Choosing host WeighedHost [host: i3computebay15, weight: 1.0] for instance 7b66bc37-cd0a-476a-a0a9-c06b84a9d31a nova-scheduler.log.1:2014-04-04 04:55:25.010 17861 INFO nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] Attempting to build 1 instance(s) uuids: [u'7b66bc37-cd0a-476a-a0a9-c06b84a9d31a'] nova-scheduler.log.1:2014-04-04 04:55:25.012 17861 ERROR nova.scheduler.filter_scheduler [req-5019a4c6-febc-4ea1-84a6-0aaef318d9a9 d8f4d6653e1b4454bf0a5fbcc7d224c6 b65b8645eea0491d8e0147a8bd6c38f6] [instance: 7b66bc37-cd0a-476a-a0a9-c06b84a9d31a] Error from last host: i3computebay15 (node i3computebay15): [u'Traceback (most recent call last):\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1065, in _build_instance\nset_access_ip=set_access_ip)\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 360, in decorated_function\nreturn function(self, context, *args, **kwargs)\n', u' File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1475, in _spawn\nLOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File /usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py, line 68, in __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u' File /usr/lib/python2.7/dist-p ackages/nova/compute/manager.py,
[Yahoo-eng-team] [Bug 1236372] Re: Router without active ports fails to be deleted, are reports wrong error message
Reviewed: https://review.openstack.org/85497
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e1fcdb25a3365c14d564d7a04ed09adda3ad1265
Submitter: Jenkins
Branch:milestone-proposed
commit e1fcdb25a3365c14d564d7a04ed09adda3ad1265
Author: sushma_korati sushma_kor...@persistent.co.in
Date: Thu Mar 27 15:03:45 2014 +0530
Changed the message line of RouterInUse class
Implements: Changed the message line of RouterInUse class,
so user will not get confused with active or inactive ports
while deleting the router.
Closes-Bug: #1236372
Change-Id: I7a82550e2c6051f9e4940a8f1dd4401059e0a8d8
(cherry picked from commit 238689570145fdafe8e61967bb56133f167d39ab)
** Changed in: neutron
Status: Fix Committed = 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/1236372
Title:
Router without active ports fails to be deleted, are reports wrong
error message
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
Version
===
Havana, RHEL, neutron+ovs, python-neutron-2013.2-0.3.3.b3.el6ost
Description
===
It's impossible to delete a router while it still has inactive ports.
The error message states that the router still has active ports.
# neutron router-port-list router1
+--+--+---+--+
| id | name | mac_address | fixed_ips
|
+--+--+---+--+
| 052a48e4-0868-4675-bef7-8f763dd697b4 | | fa:16:3e:60:73:8d |
{subnet_id: c5d63940-71e8-4338-865e-f5364fbe4e78, ip_address:
10.35.214.1} |
| 065cef02-a949-45c9-b3df-e005dbf96c9a | | fa:16:3e:a6:6d:d8 |
{subnet_id: 044bcc05-f37b-4d1d-a700-c91c4381fbc8, ip_address:
10.35.211.1} |
| 7a020243-90e5-439d-90fb-ec96b07843e7 | | fa:16:3e:04:0c:1f |
{subnet_id: 4081fbca-3e59-4be5-a98e-3c9e0d13d3a6, ip_address:
10.35.212.1} |
| 7af56958-674e-472b-8dbe-09b60501a6e6 | | fa:16:3e:1a:07:a4 |
{subnet_id: ef8e7c03-f17f-4c3c-9afe-252aca1283fd, ip_address:
10.35.170.102} |
| f034cb8a-2a09-4d41-b46c-a08fe208461e | | fa:16:3e:de:9d:32 |
{subnet_id: cca4edc7-2872-4c1e-a270-3b0beb60f421, ip_address:
10.35.213.1} |
+--+--+---+--+
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
| status| ACTIVE
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-update $i --admin_state_up False ; done | grep status
# for i in `neutron router-port-list router1 | grep subnet_id | cut -d -f
2` ; do neutron port-show $i ; done | grep status
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
| status| DOWN
|
# neutron router-delete router1
Router 727edf71-f637-402e-9fd9-767c372922ee still has active ports
From /var/log/neutron/server.log
2013-10-07 16:39:40.429 2341 ERROR neutron.api.v2.resource [-] delete failed
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2013-10-07 16:39:40.429 2341 TRACE neutron.api.v2.resource File
/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py, line 84, in
[Yahoo-eng-team] [Bug 1289139] Re: Configurable values is not printed in the OFA agent log file
Reviewed: https://review.openstack.org/85500 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=db0bffd199e959432f719dc919d410b21bd02589 Submitter: Jenkins Branch:milestone-proposed commit db0bffd199e959432f719dc919d410b21bd02589 Author: fumihiko kakuma kak...@valinux.co.jp Date: Fri Mar 7 14:03:14 2014 +0900 Log configuration values for OFA agent When other agents start up, they log the configuration values to their logs. This patch adds the same feature to the Openflow agent. fixes bug 1289139 Change-Id: Ibab20154805a12ec265a2499cbfd6c376c376130 (cherry picked from commit 7d1e49a08a170ecf4e2546b25c67d4a8d41fd34a) ** Changed in: neutron Status: Fix Committed = 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/1289139 Title: Configurable values is not printed in the OFA agent log file Status in OpenStack Neutron (virtual network service): Fix Released Bug description: When the neutron-server starts up, it prints out the configurable values in the q-svc log. This values is useful in debugging problems. Such output is not in the OFA agent's log file. related bug 1285962 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1289139/+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 1302467] Re: Logging on list operations slows down operation by about 500%
Reviewed: https://review.openstack.org/85512 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3940b430f1e72b70a758d348fb5447f0fb0aa17f Submitter: Jenkins Branch:milestone-proposed commit 3940b430f1e72b70a758d348fb5447f0fb0aa17f Author: Salvatore Orlando salv.orla...@gmail.com Date: Fri Apr 4 03:30:12 2014 -0700 Don't emit log for missing attribute check policy A missing policy for validating whether an attribute should be visible or not is a perfectly normal condition, and there is no value in logging it. Writing this information to the log is also having a considerable performance impact on list operations. Change-Id: Ie9d3ae6b249a5c49f6d81c1e56915174d8479a07 Closes-Bug: 1302467 (cherry picked from commit ef01fb553a141c012c8d8600edd6b709c5807111) ** Changed in: neutron Status: Fix Committed = 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/1302467 Title: Logging on list operations slows down operation by about 500% Status in OpenStack Neutron (virtual network service): Fix Released Bug description: On list operations, every attribute for every item returned by the plugin is checked by the policy engine to see whether the user has rights to see it [*], assuming the attribute map specifies enforce_policy=True for that attribute However, in most cases no policies are actually defined for those attributes; in this case the neutron server emits a log.debug statement for the specific attribute saying no policy was found. This statement is then repeated for every attribute without policy times the number of items in the response. Simple instrumenation shows list operations take in the API layer more than 500% the time they take in the plugin. The time is wasted after the plugin call completes and more precisely while doing policy checks. While other optimisations might be performed (such as not repeating checks already performed, and not triggering init() for each check), the biggest offender is the log statement. Some measurements are available here: http://paste.openstack.org/show/75069/ * I believe this is wrong as well, but that's another story To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302467/+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 1302091] Re: Redundant SG rule create calls in unit tests
Reviewed: https://review.openstack.org/85507 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=354bc1ab4b1490b72abf80cfd2860337f1ccb369 Submitter: Jenkins Branch:milestone-proposed commit 354bc1ab4b1490b72abf80cfd2860337f1ccb369 Author: sridhargaddam sridhar.gad...@enovance.com Date: Thu Apr 3 23:29:37 2014 +0530 Redundant SG rule create calls in unit tests This patch removes the redundant calls in the test cases. Closes-Bug: #1302091 Change-Id: I509843b427dc454c0e6b2fd2cbff1284337f (cherry picked from commit c49ec8b3ba10bb414a0f135d29ff3685e26d58b3) ** Changed in: neutron Status: Fix Committed = 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/1302091 Title: Redundant SG rule create calls in unit tests Status in OpenStack Neutron (virtual network service): Fix Released Bug description: The following test cases in TestSecurityGroups of test_extension_security_group.py file are making multiple calls to create a SG rule. test_create_security_group_rule_min_port_greater_max() test_create_security_group_rule_ports_but_no_protocol() test_create_security_group_rule_port_range_min_only() test_create_security_group_rule_port_range_max_only() test_create_security_group_rule_icmp_type_too_big() test_create_security_group_rule_icmp_code_too_big() The redundant calls can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302091/+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 1301105] Re: Second firewall creation returns 500
Reviewed: https://review.openstack.org/85513 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2436e3e543e572ac51e1d688089cb424da47e19d Submitter: Jenkins Branch:milestone-proposed commit 2436e3e543e572ac51e1d688089cb424da47e19d Author: Akihiro Motoki mot...@da.jp.nec.com Date: Wed Apr 2 11:34:01 2014 +0900 Return 409 for second firewall creation Second firewall creation returns 500, but it is an expected behavior of firewall reference implementation and an internal server error should not be returned. Change-Id: I9f537b238007d35172e2504591d9d3568ba3a41a Closes-Bug: #1301105 (cherry picked from commit 9df867c672bfb3f80511086c889b744113c56604) ** Changed in: neutron Status: Fix Committed = 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/1301105 Title: Second firewall creation returns 500 Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Second firewall creation returns 500. It is an expected behavior of firewall reference implementation and an internal server error should not be returned. It is some kind of quota error and 409 looks appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301105/+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 1301093] Re: Fixing API command for Arista Mechanism Driver
Reviewed: https://review.openstack.org/85514 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cf1c6a8adffb7cd949b701bd936ed1a15146dbad Submitter: Jenkins Branch:milestone-proposed commit cf1c6a8adffb7cd949b701bd936ed1a15146dbad Author: sukhdev sukh...@aristanetworks.com Date: Tue Apr 1 19:01:50 2014 -0700 Fixing Arista CLI command A minor change is made to the Arista API between ML2 Driver and the back-end. This fix addresses this change to align Icehouse release with Arista EOS releases. Change-Id: Ia7cd3701c76d920a7e0d1334290c73ce7e8e5576 Closes-Bug: 1301093 (cherry picked from commit f3e9b6d6dc53d2e85c9085a1e3ec11b51f803948) ** Changed in: neutron Status: Fix Committed = 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/1301093 Title: Fixing API command for Arista Mechanism Driver Status in OpenStack Neutron (virtual network service): Fix Released Bug description: A minor change is made to the Arista API between ML2 Driver and the back-end. This bug addresses this change to align Icehouse release with Arista EOS releases. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1301093/+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 1297875] Re: some tests call called_once_with_args with no assert, those lines are ignored
Reviewed: https://review.openstack.org/85503
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=5417220fc50fb31218ed1ed2aba6b926591c5f81
Submitter: Jenkins
Branch:milestone-proposed
commit 5417220fc50fb31218ed1ed2aba6b926591c5f81
Author: Miguel Angel Ajo mangel...@redhat.com
Date: Tue Mar 18 13:33:19 2014 +0100
fixes broken neutron-netns-cleanup
Some configuration parameters used in neutron.agent.linux.utils
were missing. The namespace attribute in the FakeNetwork object
was missing, and used in neutron.agent.linux.dhcp. Also, the
plugin object was missing for release_dhcp_port operation.
We provide a fake plugin object to accept current and any future
plugin calls as this is meant to be an standalone tool that
should work without any RPC connectivity.
FakeNetwork was switched for neutron.agent.linux.dhcp.NetModel
to follow any future changes in NetModel.
Two wrong called_once_with_args calls without assert were fixed.
Change-Id: Ia51ea9bd4c8eea6b250858964ad5286c933702e0
Closes-Bug: #1291915
Partial-Bug: #1297875
(cherry picked from commit 907bf41afbdb9f565c45a535f637c8928d0be52a)
** Changed in: neutron
Status: Fix Committed = 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/1297875
Title:
some tests call called_once_with_args with no assert, those lines
are ignored
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
A few tests use called_once_with_args instead of mock's
assert_called_once_with_args
without checking the result.
That means that we're not asserting for that to happen.
Those tests need to be fixed.
[majopela@f20-devstack neutron]$ grep .called_once_with * -R | grep -v
assert
neutron/tests/unit/test_dhcp_agent.py:
disable.called_once_with_args(network.id)
neutron/tests/unit/test_dhcp_agent.py:
uuid5.called_once_with(uuid.NAMESPACE_DNS, 'localhost')
neutron/tests/unit/test_post_mortem_debug.py:
mock_print_exception.called_once_with(*exc_info)
neutron/tests/unit/test_db_migration.py:
mock_open.write.called_once_with('a')
neutron/tests/unit/test_agent_netns_cleanup.py:
ovs_br_cls.called_once_with('br-int', conf.AGENT.root_helper)
neutron/tests/unit/test_metadata_agent.py:
self.eventlet.wsgi.server.called_once_with(
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1297875/+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 1299145] Re: Documentation Bug, BigSwitch should be Big Switch
Reviewed: https://review.openstack.org/85518 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8a901fd0ee6ec056184d36eca709799e6ab2e837 Submitter: Jenkins Branch:milestone-proposed commit 8a901fd0ee6ec056184d36eca709799e6ab2e837 Author: Kanzhe Jiang kan...@gmail.com Date: Fri Mar 28 11:31:56 2014 -0700 Update BigSwitch Name to its correct name Update Neutron documentation and code comments to replace BigSwitch name to Big Switch Closes-Bug: #1299145 Change-Id: I7c14f6170871b361c8929898ee6af5d1a1f41714 (cherry picked from commit 408ef55d4ef1a9d246571511203ab337ba5346c6) ** Changed in: neutron Status: Fix Committed = 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/1299145 Title: Documentation Bug, BigSwitch should be Big Switch Status in OpenStack Neutron (virtual network service): Fix Released Bug description: BigSwitch references should be changed to Big Switch. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1299145/+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 1300808] Re: Invalid version number '['3.13.0']' with Ubuntu trusty
Reviewed: https://review.openstack.org/85515 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea6b2b9cfaee9053639649935e9659e0bcff286c Submitter: Jenkins Branch:milestone-proposed commit ea6b2b9cfaee9053639649935e9659e0bcff286c Author: Simon Pasquier simon.pasqu...@bull.net Date: Tue Apr 1 15:55:55 2014 +0200 Fix function parsing the kernel version Change-Id: Id56efb476144a18cd9eb7279bc0f602760a86173 Closes-Bug: #1300808 (cherry picked from commit d4fdac7ae596888b8e83d9559019eafb728cd3fe) ** Changed in: neutron Status: Fix Committed = 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/1300808 Title: Invalid version number '['3.13.0']' with Ubuntu trusty Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Running latest devstack on Trusty Ubuntu, the Neutron agent fails to start with the following backtrace: 2014-04-01 13:49:54.227 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['uname', '-r'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.232 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['uname', '-r'] Exit code: 0 Stdout: '3.13.0-20-generic\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.233 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Running command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] from (pid=14900) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-04-01 13:49:54.348 DEBUG neutron.agent.linux.utils [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Command: ['sudo', '/usr/local/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--version'] Exit code: 0 Stdout: 'ovs-vsctl (Open vSwitch) 2.0.1\nCompiled Feb 23 2014 14:42:32\n' Stderr: '' from (pid=14900) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-04-01 13:49:54.349 DEBUG neutron.agent.linux.ovs_lib [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] Checking OVS version for VXLAN support installed klm version is None, installed Linux version is ['3.13.0'], installed user version is 2.0 from (pid=14900) check_ovs_vxlan_version /opt/stack/neutron/neutron/agent/linux/ovs_lib.py:541 2014-04-01 13:49:54.350 CRITICAL neutron [req-9f04e437-c667-40c2-8be4-aef96f4810de None None] invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron Traceback (most recent call last): 2014-04-01 13:49:54.350 TRACE neutron File /usr/local/bin/neutron-openvswitch-agent, line 10, in module 2014-04-01 13:49:54.350 TRACE neutron sys.exit(main()) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 1360, in main 2014-04-01 13:49:54.350 TRACE neutron agent = OVSNeutronAgent(**agent_config) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 214, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self._check_ovs_version() 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py, line 232, in _check_ovs_version 2014-04-01 13:49:54.350 TRACE neutron ovs_lib.check_ovs_vxlan_version(self.root_helper) 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 550, in check_ovs_vxlan_version 2014-04-01 13:49:54.350 TRACE neutron 'kernel', 'VXLAN') 2014-04-01 13:49:54.350 TRACE neutron File /opt/stack/neutron/neutron/agent/linux/ovs_lib.py, line 507, in _compare_installed_and_required_version 2014-04-01 13:49:54.350 TRACE neutron installed_kernel_version) = dist_version.StrictVersion( 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 40, in __init__ 2014-04-01 13:49:54.350 TRACE neutron self.parse(vstring) 2014-04-01 13:49:54.350 TRACE neutron File /usr/lib/python2.7/distutils/version.py, line 107, in parse 2014-04-01 13:49:54.350 TRACE neutron raise ValueError, invalid version number '%s' % vstring 2014-04-01 13:49:54.350 TRACE neutron ValueError: invalid version number '['3.13.0']' 2014-04-01 13:49:54.350 TRACE neutron q-agt failed to start This is due to bug #1291535 and this fix: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b2f65d9d447ddf2caf3b9c754bd00a5148bdf12c To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300808/+subscriptions -- Mailing list:
[Yahoo-eng-team] [Bug 1300628] Re: BigSwitch ML2 driver uses portbindingsports table
Reviewed: https://review.openstack.org/85517 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f367d7422c669fda908b5ef0228cde9dc5717f63 Submitter: Jenkins Branch:milestone-proposed commit f367d7422c669fda908b5ef0228cde9dc5717f63 Author: Kevin Benton blak...@gmail.com Date: Tue Apr 1 01:05:29 2014 -0700 Stop using portbindings_db in BSN ML2 driver Avoids using the portbindings_db in the Big Switch ML2 driver since ML2 has deprecated that database for its own version that tracks the same information. Also eliminates unnecessary 'binding_host' field since it is now always the same as as the 'portbinding:host_id' field. Closes-Bug: #1300628 Change-Id: I17d47cb446cdd2e989c3e0d01b797a81309faaa7 (cherry picked from commit c70c2719d700902854ef0381cb725722ac2da05e) ** Changed in: neutron Status: Fix Committed = 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/1300628 Title: BigSwitch ML2 driver uses portbindingsports table Status in OpenStack Neutron (virtual network service): Fix Released Bug description: The Big Switch ML2 driver references the deprecated portbindings_db in the port location tracking code. This needs to be removed because it's resulting in the entire portbinding_db schema for one small function. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300628/+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 1293508] Re: NSX plugin: 400 should be returned on invalid certificate
Reviewed: https://review.openstack.org/85506 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d56f12d4676c1cc26d0da80e053da07e0253dbe8 Submitter: Jenkins Branch:milestone-proposed commit d56f12d4676c1cc26d0da80e053da07e0253dbe8 Author: Salvatore Orlando salv.orla...@gmail.com Date: Fri Mar 14 17:43:42 2014 -0700 NSX plugin: return 400 for invalid gw certificate Gateway certificates are validated by the NSX backend. The code currently treats a failure in certification validation as a backend failure and therefore returns a 500 status code. This patch changes this behaviour by returning a 400 status code and an appropriate error description. To this aim a handler for 400 errors has been added to the NSX API client. Closes-Bug: #1293508 Change-Id: I196f14337e47cd40710a6d8a30bbe1cac5ffe05b (cherry picked from commit 13c9f3b813f5bb368e311ba0d428fa759d68289a) ** Changed in: neutron Status: Fix Committed = 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/1293508 Title: NSX plugin: 400 should be returned on invalid certificate Status in OpenStack Neutron (virtual network service): Fix Released Bug description: When a gateway device is created, the client certificate is not stored anywhere on the neutron server, but then passed directly to the backend, which validates the certificate. Currently the NSX backend raises an exception when the certificate is not valid. This exception is treated by the NSX plugin as a backend failure and a 500 is then returned. However, the correct error would a 400 with an appropriate error message. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1293508/+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 1291915] Re: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken
Reviewed: https://review.openstack.org/85503 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5417220fc50fb31218ed1ed2aba6b926591c5f81 Submitter: Jenkins Branch:milestone-proposed commit 5417220fc50fb31218ed1ed2aba6b926591c5f81 Author: Miguel Angel Ajo mangel...@redhat.com Date: Tue Mar 18 13:33:19 2014 +0100 fixes broken neutron-netns-cleanup Some configuration parameters used in neutron.agent.linux.utils were missing. The namespace attribute in the FakeNetwork object was missing, and used in neutron.agent.linux.dhcp. Also, the plugin object was missing for release_dhcp_port operation. We provide a fake plugin object to accept current and any future plugin calls as this is meant to be an standalone tool that should work without any RPC connectivity. FakeNetwork was switched for neutron.agent.linux.dhcp.NetModel to follow any future changes in NetModel. Two wrong called_once_with_args calls without assert were fixed. Change-Id: Ia51ea9bd4c8eea6b250858964ad5286c933702e0 Closes-Bug: #1291915 Partial-Bug: #1297875 (cherry picked from commit 907bf41afbdb9f565c45a535f637c8928d0be52a) ** Changed in: neutron Status: Fix Committed = 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/1291915 Title: neutron-netns-cleanup script doesn't work in icehouse/havana, code is broken Status in OpenStack Neutron (virtual network service): Fix Released Bug description: 1st) Some configuration options are not registered on the tool, but they're used in neutron.agent.linux.dhcp during execution $ neutron-netns-cleanup --debug --force --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini 2014-03-12 14:55:44.791 INFO neutron.common.config [-] Logging enabled! 2014-03-12 14:55:44.792 DEBUG neutron.agent.linux.utils [-] Running command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] from (pid=1785) create_process /opt/stack/neutron/neutron/agent/linux/utils.py:48 2014-03-12 14:55:45.001 DEBUG neutron.agent.linux.utils [-] Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list'] Exit code: 0 Stdout: 'qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2\nqrouter-acc5f724-a169-4ffc-9e81-f00d43954509\nqrouter-5ed23337-9538-4994-823f-c64720506e54\n' Stderr: '' from (pid=1785) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 14:55:47.006 ERROR neutron.agent.linux.dhcp [-] Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth Error importing interface driver 'neutron.agent.linux.interface.OVSInterfaceDriver': no such option: ovs_use_veth 2nd) When we try to destroy a network, there's a dependency on the .namespace attribute of the network, that wasn't before. Stderr: '' from (pid=1969) execute /opt/stack/neutron/neutron/agent/linux/utils.py:74 2014-03-12 15:08:53.048 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace: qdhcp-65cb66de-82d0-407c-aa23-2c544528f0d2 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util Traceback (most recent call last): 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 131, in destroy_namespace 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util kill_dhcp(conf, namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/netns_cleanup_util.py, line 86, in kill_dhcp 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util dhcp_driver.disable() 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 181, in disable 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.device_manager.destroy(self.network, self.interface_name) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util File /opt/stack/neutron/neutron/agent/linux/dhcp.py, line 814, in destroy 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util self.driver.unplug(device_name, namespace=network.namespace) 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util AttributeError: 'FakeNetwork' object has no attribute 'namespace' 2014-03-12 15:08:53.048 TRACE neutron.agent.netns_cleanup_util 3rd) This error will happen because no plugin rpc connection is provided, and that's used in /opt/stack/neutron/neutron/agent/linux/dhcp.py as self.plugin.release_dhcp_port 2014-03-13 12:00:07.880 ERROR neutron.agent.netns_cleanup_util [-] Error unable to destroy namespace:
[Yahoo-eng-team] [Bug 1295854] Re: NSX plugin does not support pagination
Reviewed: https://review.openstack.org/85522 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=70df0be32b0eabe0ae97e202ee215752d724ff3e Submitter: Jenkins Branch:milestone-proposed commit 70df0be32b0eabe0ae97e202ee215752d724ff3e Author: armando-migliaccio arma...@gmail.com Date: Fri Mar 21 14:48:19 2014 -0700 NSX: Fix pagination support Add pagination support to the base plugin, leaving the service plugin unaltered. Minor tweaks to the UT where required to avoid intermittent failures caused by random ordering. Closes-bug: 1295854 Change-Id: I03e9e104967716046909d6120426e879f714a5c8 (cherry picked from commit 16ce0ae2c2b50b4317cdb95e62246d805b3d76a9) ** Changed in: neutron Status: Fix Committed = 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/1295854 Title: NSX plugin does not support pagination Status in OpenStack Neutron (virtual network service): Fix Released Bug description: This should be rectified. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1295854/+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 1288582] Re: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute
Reviewed: https://review.openstack.org/85499 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a5909c079f89f86bd6ca2c764c0c94c8707a555a Submitter: Jenkins Branch:milestone-proposed commit a5909c079f89f86bd6ca2c764c0c94c8707a555a Author: Aaron Rosen aaronoro...@gmail.com Date: Mon Mar 31 11:03:48 2014 -0700 Only send notifications on uuid device_id's Neutron assumes that all ports with the device_owner that start with 'compute:' are ports created by nova compute. Thus, when the debug agent creates a port with device_owner = compute:probe the nova notifier feature tells nova when this port is wired even though nova does not know about it (doesn't really matter we just log an error). This patch adds a check to make sure the device_id is a uuid as nova only uses uuids and the debug agent uses the hostname for device_id. Change-Id: I04e7195a1fb30bc37e1c0141315c053174f8722c Closes-bug: #1288582 (cherry picked from commit 6b4fecb9de0aa80e66b31555001dca95d14c789f) ** Changed in: neutron Status: Fix Committed = 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/1288582 Title: Rename DEVICE_OWNER_COMPUTE_PROBE to not start with compute Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Neutron assumes that all ports with the device_owner that start with 'compute' are ports created by nova compute. Thus, when the debug agent creates a port with device_owner = compute:probe the nova callback feature tells nova when this port is wired even though nova does not know about (doesn't really matter we just log an error). This patch just renames this device_owner to not start with compute to avoid this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1288582/+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 1294526] Re: floatingip's id should be used instead of floatingip itself
Reviewed: https://review.openstack.org/85525 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fd757c79af3503b28225fe65e089ff7cda17c678 Submitter: Jenkins Branch:milestone-proposed commit fd757c79af3503b28225fe65e089ff7cda17c678 Author: Yong Sheng Gong gong...@unitedstack.com Date: Wed Mar 19 16:14:33 2014 +0800 use floatingip's ID as key instead of itself Change-Id: I267f174a0e2e611ec007404c7b44e2c73a359c38 Closes-Bug: 1294526 (cherry picked from commit 7120325d37df414d8de084c5b41fdfbea3a06565) ** Changed in: neutron Status: Fix Committed = 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/1294526 Title: floatingip's id should be used instead of floatingip itself Status in OpenStack Neutron (virtual network service): Fix Released Bug description: https://github.com/openstack/neutron/blob/master/neutron/agent/l3_agent.py#L476 this id should be used as hash key instead of floating ip itself To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1294526/+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 1302007] Re: l3 agent uses method concatenating two constants
Reviewed: https://review.openstack.org/85526 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=90039e87503767bafef27b90189fa47dfb7f5b21 Submitter: Jenkins Branch:milestone-proposed commit 90039e87503767bafef27b90189fa47dfb7f5b21 Author: Jakub Libosvar libos...@redhat.com Date: Thu Apr 3 14:52:59 2014 +0200 Set ns_name in RouterInfo as attribute Closes-Bug: #1302007 Change-Id: I02a9b92eea06010569d3d9c5a987e69f89b23be5 (cherry picked from commit ceee7b4ac9d027499dfd2568868f1192bfb77879) ** Changed in: neutron Status: Fix Committed = 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/1302007 Title: l3 agent uses method concatenating two constants Status in OpenStack Neutron (virtual network service): Fix Released Bug description: In l3 agent is method ns_name() that concatenates constant NS_PREFIX with router.id that doesn't change during router's lifecycle. It's ineffective, namespace name can be an instance attribute. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302007/+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
