[Yahoo-eng-team] [Bug 1685732] Re: create_keystone_accounts error on latest devstack ocata branch(Ubuntu 16.04 LTS)

[Isaku Yamahata]

As there is no indication that this is related to networking-odl and this is 
marked as invalid in keystone.
unlink this report from networking-odl


** No longer affects: networking-odl

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

Title:
  create_keystone_accounts error on latest devstack ocata branch(Ubuntu
  16.04 LTS)

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Hi All,

  Im seeing this error on latest stable/ocata branch. I tried multiple
  reclones with repeated "./unstack.sh; ./clean.sh; ./stack.sh", but the
  issue is not getting fixed. I have raised the same issue in ask
  openstack(https://ask.openstack.org/en/question/105736
  /create_keystone_accounts-error-on-latest-devstack-ocata-
  branchubuntu-1604-lts/)

  Logs below:

  ./stack.sh Error logs:
  +
  2017-04-24 12:09:09.942 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created user admin
  2017-04-24 12:09:10.008 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created role admin
  2017-04-24 12:09:10.075 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Granted admin on admin to 
user admin.
  2017-04-24 12:09:10.199 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created region RegionOne
  2017-04-24 12:09:10.366 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created admin endpoint 
http://192.168.0.103/identity_admin
  2017-04-24 12:09:10.451 INFO keystone.cmd.cli 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Created public endpoint 
http://192.168.0.103/identity
  2017-04-24 12:09:10.455 INFO keystone.assignment.core 
[req-b7616d45-5e27-48f5-b65a-a5c0c8cdd3c0 None None] Creating the default role 
9fe2ff9ee4384b1894a90878d3e92bab because it does not exist.
  +./stack.sh:main:1076  create_keystone_accounts
  +lib/keystone:create_keystone_accounts:328  local admin_project
  ++lib/keystone:create_keystone_accounts:329  openstack project show admin -f 
value -c id
  Failed to discover available identity versions when contacting 
http://192.168.0.103/identity_admin. Attempting to parse version from URL.
  Could not determine a suitable URL for the plugin
  +lib/keystone:create_keystone_accounts:329  admin_project=
  +lib/keystone:create_keystone_accounts:1   exit_trap
  +./stack.sh:exit_trap:492  local r=1
  ++./stack.sh:exit_trap:493  jobs -p
  +./stack.sh:exit_trap:493  jobs=
  +./stack.sh:exit_trap:496  [[ -n '' ]]
  +./stack.sh:exit_trap:502  kill_spinner
  +./stack.sh:kill_spinner:388   '[' '!' -z '' ']'
  +./stack.sh:exit_trap:504  [[ 1 -ne 0 ]]
  +./stack.sh:exit_trap:505  echo 'Error on exit'
  Error on exit
  +./stack.sh:exit_trap:506  generate-subunit 1493015271 684 
fail
  +./stack.sh:exit_trap:507  [[ -z /opt/stack/logs ]]
  +./stack.sh:exit_trap:510  
/home/stack/openstack-repo/stable/ocata/tools/worlddump.py -d /opt/stack/logs
  World dumping... see /opt/stack/logs/worlddump-2017-04-24-063916.txt for 
details
  +./stack.sh:exit_trap:516  exit 1

  Other logs:
  ++
  stack@controller:/etc/apache2$ grep -rn identity* | grep wsgi
  sites-available/keystone-wsgi-admin.conf:1:ProxyPass "/identity_admin" 
"unix:/var/run/uwsgi/keystone-wsgi-admin.socket|uwsgi://uwsgi-uds-keystone-wsgi-admin/"
 retry=0 
  sites-available/keystone.conf:56:Alias /identity /usr/bin/keystone-wsgi-public
  sites-available/keystone.conf:66:Alias /identity_admin 
/usr/bin/keystone-wsgi-admin
  sites-available/keystone-wsgi-public.conf:1:ProxyPass "/identity" 
"unix:/var/run/uwsgi/keystone-wsgi-public.socket|uwsgi://uwsgi-uds-keystone-wsgi-public/"
 retry=0 

  
  stack@controller:/etc/apache2$ ps -ef | grep wsgi
  stack 4071  3900  0 12:09 pts/20   00:00:00 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-public.ini
  stack 4129  4071  1 12:09 pts/20   00:00:02 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-public.ini
  stack 4130  4071  1 12:09 pts/20   00:00:02 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-public.ini
  stack   4263  0 12:09 pts/21   00:00:00 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-admin.ini
  stack 4461    1 12:09 pts/21   00:00:03 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-admin.ini
  stack 4462    1 12:09 pts/21   00:00:03 /usr/local/bin/uwsgi --ini 
/etc/keystone/keystone-uwsgi-admin.ini
  stack 5320  5977  0 12:12 pts/17   00:00:00 grep --color=auto wsgi

  stack@controller:/etc/apache2$ sudo netstat | grep 35357
  stack@controller:/etc/apache2$ 

  
  Please let me know if anymore info is 

[Yahoo-eng-team] [Bug 1706854] Re: KeyErorr in _update_router_gw_port

[Isaku Yamahata]

recently we don't see the exception. so for now it's closed.


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

** Changed in: networking-odl
   Status: New => Invalid

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

Title:
  KeyErorr in _update_router_gw_port

Status in networking-odl:
  Invalid
Status in neutron:
  Invalid

Bug description:
  subnet creation fails with KeyError excpetion in _update_router_gw_port
  
http://logs.openstack.org/47/452647/13/check/gate-tempest-dsvm-networking-odl-boron-snapshot-v2driver/e1316ac/logs/screen-q-svc.txt.gz?#_Jul_27_02_52_16_838534

  It looks like network dictionary includes old subnets

  
  Jul 27 02:52:16.838534 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation [None 
req-4df03464-cf1d-4f13-a915-7ca2026a9831 admin admin] POST failed.: KeyError: 
u'af542c21-0fa2-441b-9ca9-746d2193e4d5'
  Jul 27 02:52:16.838725 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation Traceback 
(most recent call last):
  Jul 27 02:52:16.838923 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/pecan/core.py", line 683, in __call__
  Jul 27 02:52:16.839074 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
self.invoke_controller(controller, args, kwargs, state)
  Jul 27 02:52:16.839258 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/pecan/core.py", line 574, in 
invoke_controller
  Jul 27 02:52:16.839425 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation result = 
controller(*args, **kwargs)
  Jul 27 02:52:16.839583 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 94, in wrapped
  Jul 27 02:52:16.839737 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
setattr(e, '_RETRY_EXCEEDED', True)
  Jul 27 02:52:16.839890 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Jul 27 02:52:16.840045 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
self.force_reraise()
  Jul 27 02:52:16.840232 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Jul 27 02:52:16.840385 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
six.reraise(self.type_, self.value, self.tb)
  Jul 27 02:52:16.840542 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 90, in wrapped
  Jul 27 02:52:16.840697 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation return 
f(*args, **kwargs)
  Jul 27 02:52:16.840852 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 150, in wrapper
  Jul 27 02:52:16.841000 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
ectxt.value = e.inner_exc
  Jul 27 02:52:16.841203 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Jul 27 02:52:16.841354 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
self.force_reraise()
  Jul 27 02:52:16.841504 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Jul 27 02:52:16.841652 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation 
six.reraise(self.type_, self.value, self.tb)
  Jul 27 02:52:16.841801 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: ERROR neutron.pecan_wsgi.hooks.translation   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 138, in wrapper
  Jul 27 02:52:16.841955 ubuntu-xenial-citycloud-kna1-10108288 
neutron-server[19730]: 

[Yahoo-eng-team] [Bug 1711165] Re: Error during full sync with QoS

[Isaku Yamahata]

** Also 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/1711165

Title:
  Error during full sync with QoS

Status in networking-odl:
  New
Status in neutron:
  New

Bug description:
  Error when specifying qos extension driver and service plugin:

  2017-08-15 17:47:41.859 64185 INFO neutron.wsgi [-] 192.168.24.3 "OPTIONS / 
HTTP/1.0" status: 200  len: 249 time: 0.0029640
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
[req-5a639c24-7563-4b14-9f42-7d151264fe84 - - - - -] Failed during periodic 
task operation full_sync.: TypeError: get_objects() argument after ** must be a 
mapping, not NoneType
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
Traceback (most recent call last):
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File 
"/usr/lib/python2.7/site-packages/networking_odl/journal/periodic_task.py", 
line 61, in _execute_op
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
operation(context=context)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", 
line 84, in full_sync
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
collection_name)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", 
line 120, in _sync_resources
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
resources = obj_getter(context)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File "/usr/lib/python2.7/site-packages/neutron/db/db_base_plugin_common.py", 
line 62, in inner_filter
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
result = f(*args, **kwargs)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File "/usr/lib/python2.7/site-packages/neutron/db/db_base_plugin_common.py", 
line 48, in inner
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
result = f(*args, **kwargs)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task   
File "/usr/lib/python2.7/site-packages/neutron/services/qos/qos_plugin.py", 
line 267, in get_policies
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
**filters)
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task 
TypeError: get_objects() argument after ** must be a mapping, not NoneType
  2017-08-15 17:47:42.007 63696 ERROR networking_odl.journal.periodic_task

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1711165/+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 1712109] [NEW] queens: assess CI logs and file them if necessary

[Isaku Yamahata]

Public bug reported:

queens: assess CI logs and file them if necessary

** Affects: networking-odl
 Importance: Undecided
 Status: New

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** No longer affects: neutron

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

Title:
  queens: assess CI logs and file them if necessary

Status in networking-odl:
  New

Bug description:
  queens: assess CI logs and file them if necessary

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1712109/+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 1611533] Re: ml2 transaction_guard broke out of tree plugins

[Isaku Yamahata]

** Changed in: networking-odl
   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/1611533

Title:
  ml2 transaction_guard broke out of tree plugins

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

Bug description:
  recent change [1] broke l3 plugin for networking-midonet.

  [1] I9924600c57648f7eccaa5abb6979419d9547a2ff

  l3 plugins for networking-odl and dragonflow seem to have similar code
  and would be affected too.

  eg.
  
http://logs.openstack.org/87/199387/36/check/gate-tempest-dsvm-networking-midonet-ml2/ceb0331/logs/q-svc.txt.gz?level=TRACE

  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource 
[req-af588d02-2944-411f-aa22-eafca4fdabeb 
tempest-TestSecurityGroupsBasicOps-509565194 -] remove_router_interface failed: 
No details.
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource Traceback (most 
recent call last):
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource result = 
method(request=request, **args)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 151, in wrapper
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource ectxt.value = 
e.inner_exc
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 139, in wrapper
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource return 
f(*args, **kwargs)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 217, in _handle_action
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource ret_value = 
getattr(self._plugin, name)(*arg_list, **kwargs)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py", line 48, in 
wrapper
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource return 
method(*args, **kwargs)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/networking-midonet/midonet/neutron/services/l3/l3_midonet.py", 
line 190, in remove_router_interface
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context, 
router_id, interface_info)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 1756, in 
remove_router_interface
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context, 
router_id, interface_info)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 924, in 
remove_router_interface
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context, 
router_id, subnet_id, device_owner)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 901, in 
_remove_interface_by_subnet
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource 
l3_port_check=False)
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/common/utils.py", line 611, in inner
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource raise 
RuntimeError(_("Method cannot be called within a "
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource RuntimeError: 
Method cannot be called within a transaction.
  2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource 
  2016-08-09 12:31:58.293 25876 ERROR neutron.api.v2.resource 
[req-c9ae4bf8-2baf-4327-be58-bb3006b4d9c9 
tempest-TestSecurityGroupsBasicOps-2112515119 -] delete failed: No details.
  2016-08-09 12:31:58.293 25876 ERROR neutron.api.v2.resource Traceback (most 
recent call last):
  2016-08-09 12:31:58.293 25876 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource
  2016-08-09 12:31:58.293 25876 ERROR neutron.api.v2.resource result = 
method(request=request, **args)
  2016-08-09 12:31:58.293 25876 ERROR 

[Yahoo-eng-team] [Bug 1557976] Re: sg events callback: sg group deleted but the related rules are left

[Isaku Yamahata]

Required callback is added and networking-odl is also updated.


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

** Changed in: networking-odl
   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/1557976

Title:
  sg events callback: sg group deleted but the related rules are left

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

Bug description:
  v1 driver use the AFTER_ event, but sg pass down from plugin just
  includes the id, we can not delete the rules related to the sg group
  base on it.

  and after we get the sg with right rules, we need emit several rule
  delete operation into journal thread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1557976/+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 1546910] Re: args pass to securitygroup precommit event should include the complete info

[Isaku Yamahata]

** Changed in: networking-odl
   Status: New => Fix Released

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

Title:
  args pass to securitygroup precommit event should include the complete
  info

Status in networking-odl:
  Fix Released
Status in networking-odl 3.0-newton series:
  New
Status in neutron:
  Fix Released

Bug description:
  We introduced the PRECOMMIT_XXX event, but in securitygroups_db.py,
  the kwargs passed to it do not include the complete info of DB like
  AFTER_XXX event. For example, the id of the new created sg/rule.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1546910/+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 1698284] [NEW] precommit of securitygroup/rule is missing necessary info

[Isaku Yamahata]

Public bug reported:

https://review.openstack.org/#/c/284738/
breaks mechanism driver. especially networking-odl

precommit callbacks of security group/security group rule creation are missing 
necessary info.
They should pass more info. For example id, egress/ingress_rule as deafult rule.
Before ovo patch, those information can retrieved from context.session.new.
However with ovo patch, those newly created orm object is dropped from session 
as
NeutronDbObject expung itself when it's created. See 
neutron.objects.base._detach_db_obj for db relationship.

** Affects: networking-odl
 Importance: Critical
 Assignee: Isaku Yamahata (yamahata)
 Status: In Progress

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: In Progress

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
   Importance: Undecided => Critical

** Changed in: networking-odl
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

** Changed in: networking-odl
Milestone: None => 11.0.0

** Changed in: neutron
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

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

Title:
  precommit of securitygroup/rule is missing necessary info

Status in networking-odl:
  In Progress
Status in neutron:
  In Progress

Bug description:
  https://review.openstack.org/#/c/284738/
  breaks mechanism driver. especially networking-odl

  precommit callbacks of security group/security group rule creation are 
missing necessary info.
  They should pass more info. For example id, egress/ingress_rule as deafult 
rule.
  Before ovo patch, those information can retrieved from context.session.new.
  However with ovo patch, those newly created orm object is dropped from 
session as
  NeutronDbObject expung itself when it's created. See 
neutron.objects.base._detach_db_obj for db relationship.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1698284/+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 1675891] [NEW] ML2: create_network_precommit isn't passed MTU and AZ

[Isaku Yamahata]

Public bug reported:

create_network_precommit passed to mechanism driver isn't passed MTU and
AZ.

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

Title:
  ML2: create_network_precommit isn't passed MTU and AZ

Status in neutron:
  New

Bug description:
  create_network_precommit passed to mechanism driver isn't passed MTU
  and AZ.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1675891/+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 1673876] [NEW] vlan_transparency=True is always rejected by logger mechanism driver

[Isaku Yamahata]

Public bug reported:

network creation with vlan_transparency=True always fails with logger
mechanism driver enabled.

This is because logger mechanism driver doesn't know vlan transparency and 
rejects it.
logger mechanism driver shouldn't do.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1673876

Title:
  vlan_transparency=True is always rejected by logger mechanism driver

Status in neutron:
  In Progress

Bug description:
  network creation with vlan_transparency=True always fails with logger
  mechanism driver enabled.

  This is because logger mechanism driver doesn't know vlan transparency and 
rejects it.
  logger mechanism driver shouldn't do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1673876/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Also affects: networking-midonet
   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/1608980

Title:
  Remove MANIFEST.in as it is not explicitly needed by PBR

Status in anvil:
  Invalid
Status in craton:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in gce-api:
  Fix Released
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kosmos:
  Fix Released
Status in Magnum:
  Fix Released
Status in masakari:
  Fix Released
Status in networking-midonet:
  New
Status in networking-odl:
  New
Status in neutron:
  Fix Released
Status in Neutron LBaaS Dashboard:
  Confirmed
Status in octavia:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-searchlightclient:
  In Progress
Status in OpenStack Search (Searchlight):
  Fix Released
Status in Solum:
  Fix Released
Status in Swift Authentication:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in Tricircle:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  PBR do not explicitly require MANIFEST.in, so it can be removed.

  
  Snippet from: http://docs.openstack.org/infra/manual/developers.html

  Manifest

  Just like AUTHORS and ChangeLog, why keep a list of files you wish to
  include when you can find many of these in git. MANIFEST.in generation
  ensures almost all files stored in git, with the exception of
  .gitignore, .gitreview and .pyc files, are automatically included in
  your distribution. In addition, the generated AUTHORS and ChangeLog
  files are also included. In many cases, this removes the need for an
  explicit ‘MANIFEST.in’ file

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1608980/+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 1650351] Re: test_service_providers.test_service_providers_list runs unconditionally

[Isaku Yamahata]

** Also 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/1650351

Title:
  test_service_providers.test_service_providers_list runs
  unconditionally

Status in neutron:
  In Progress
Status in tempest:
  In Progress

Bug description:
  test_service_providers.test_service_providers_list requires neutron 
service-type extension.
  It's enabled by default from Newton. So by default it fails with mitaka(or 
older).

  The test case needs to be skipped when service-type extension isn't
  enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1650351/+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 1648095] Re: neutron-ns-metadata-proxy cleanup does not occur

[Isaku Yamahata]

** Also 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/1648095

Title:
  neutron-ns-metadata-proxy cleanup does not occur

Status in networking-odl:
  In Progress
Status in neutron:
  In Progress

Bug description:
  Devstack + newton + networking-odl / v2.
  To reproduce:
  1. Create a new vxlan network.
  2. Add 1 or more subnets
  3. Delete the network.
  I notice this occur during 
tempest.api.network.test_networks.NetworksIpV6Test.test_create_list_subnet_with_no_gw64_one_network

  Finally linux is Out of memory and terminating processes based on
  score.

  Many like this;
  stack 2538 1  0 11:19 ?00:00:00 /usr/bin/python 
/usr/local/bin/neutron-ns-metadata-proxy 
--pid_file=/opt/stack/data/neutron/external/pids/b408d77c-ca69-4b2c-b2f1-5a889f149f11.pid
 --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy 
--network_id=b408d77c-ca69-4b2c-b2f1-5a889f149f11 
--state_path=/opt/stack/data/neutron --metadata_port=80 
--metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
  stack 2981 1  0 11:20 ?00:00:00 /usr/bin/python 
/usr/local/bin/neutron-ns-metadata-proxy 
--pid_file=/opt/stack/data/neutron/external/pids/ddfc2980-2c16-46f4-8eab-e91a047e796c.pid
 --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy 
--network_id=ddfc2980-2c16-46f4-8eab-e91a047e796c 
--state_path=/opt/stack/data/neutron --metadata_port=80 
--metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
  stack 4977 1  0 11:28 ?00:00:00 /usr/bin/python 
/usr/local/bin/neutron-ns-metadata-proxy 
--pid_file=/opt/stack/data/neutron/external/pids/2b6d0fe6-f13a-4be4-9ea6-f6bc12ed3d69.pid
 --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy 
--network_id=2b6d0fe6-f13a-4be4-9ea6-f6bc12ed3d69 
--state_path=/opt/stack/data/neutron --metadata_port=80 
--metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
  stack 6199 12085  0 11:34 pts/600:00:00 grep neutron-ns-metadata-proxy
  stack29462 1  0 11:11 ?00:00:00 /usr/bin/python 
/usr/local/bin/neutron-ns-metadata-proxy 
--pid_file=/opt/stack/data/neutron/external/pids/00192768-29d1-46d2-9092-7a7bbd7b55ef.pid
 --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy 
--network_id=00192768-29d1-46d2-9092-7a7bbd7b55ef 
--state_path=/opt/stack/data/neutron --metadata_port=80 
--metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug
  stack32627 1  0 11:17 ?00:00:00 /usr/bin/python 
/usr/local/bin/neutron-ns-metadata-proxy 
--pid_file=/opt/stack/data/neutron/external/pids/b2aa9b47-b55e-4b3f-bf2c-31bc91d86b33.pid
 --metadata_proxy_socket=/opt/stack/data/neutron/metadata_proxy 
--network_id=b2aa9b47-b55e-4b3f-bf2c-31bc91d86b33 
--state_path=/opt/stack/data/neutron --metadata_port=80 
--metadata_proxy_user=1000 --metadata_proxy_group=1000 --debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1648095/+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 1514823] Re: Opendaylight driver shim still present in neutron tree

[Isaku Yamahata]

** Changed in: networking-odl
   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/1514823

Title:
  Opendaylight driver shim still present in neutron tree

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

Bug description:
  The opendaylight ML2 mechanism driver should be completely removed
  from the neutron tree. All opendaylight driver code and artifacts
  should be contained in the networking-odl sub-project.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1514823/+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 1454372] Re: ImportError: neutron.hooks.setup_hook

[Isaku Yamahata]

** Changed in: networking-odl
   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/1454372

Title:
  ImportError: neutron.hooks.setup_hook

Status in networking-6wind:
  Fix Committed
Status in networking-brocade:
  Fix Committed
Status in networking-odl:
  Fix Released
Status in networking-ovn:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  Attempting to pip install master gets "ImportError:
  neutron.hooks.setup_hook":

  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
ERROR:root:Error parsing
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
Traceback (most recent call last):
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40   File 
"/tmp/pip-akMy3T-build/pbr-0.11.0-py2.7.egg/pbr/core.py", line 109, in pbr
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
attrs = util.cfg_to_args(path)
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40   File 
"/tmp/pip-akMy3T-build/pbr-0.11.0-py2.7.egg/pbr/util.py", line 230, in 
cfg_to_args
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
hook_fn = resolve_name(hook)
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40   File 
"/tmp/pip-akMy3T-build/pbr-0.11.0-py2.7.egg/pbr/util.py", line 185, in 
resolve_name
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
raise ImportError(name)
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
ImportError: neutron.hooks.setup_hook
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 error 
in setup command: Error parsing /tmp/pip-akMy3T-build/setup.cfg: ImportError: 
neutron.hooks.setup_hook
  2015-05-12 17:28:14 INFO unit.nova-compute/0.install logger.go:40 
Complete output from command python setup.py egg_info:

  If I revert commit 8db41f04d54526104920f3a160203ecf7ef453b0, the error
  goes away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-6wind/+bug/1454372/+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 1649733] Re: TypeError: IPAddress('172.19.0.2') is not JSON serializable

[Isaku Yamahata]

** Changed in: networking-odl
   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/1649733

Title:
  TypeError: IPAddress('172.19.0.2') is not JSON serializable

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

Bug description:
  "TypeError: IPAddress('172.19.0.2') is not JSON serializable" seen on
  gate

  eg. http://logs.openstack.org/51/410451/1/check/gate-tempest-dsvm-
  networking-midonet-ml2-ubuntu-
  xenial/b810ef8/logs/screen-q-svc.txt.gz#_2016-12-13_23_29_12_286

  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
[req-b4c0541f-8e87-4539-a8ad-c4a2b10098cf admin -] update failed: No details.
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource Traceback (most 
recent call last):
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource result = 
method(request=request, **args)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 612, in update
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
self._update(request, id, body, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 92, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource setattr(e, 
'_RETRY_EXCEEDED', True)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 88, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*args, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 151, in wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource ectxt.value = 
e.inner_exc
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 139, in wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*args, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 128, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
traceback.format_exc())
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 123, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*dup_args, **dup_kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 660, in _update
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource obj = 
obj_updater(request.context, id, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py", line 48, in 
wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
method(*args, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 

[Yahoo-eng-team] [Bug 1649733] Re: TypeError: IPAddress('172.19.0.2') is not JSON serializable

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
   Importance: Undecided => Critical

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

Title:
  TypeError: IPAddress('172.19.0.2') is not JSON serializable

Status in networking-midonet:
  In Progress
Status in networking-odl:
  New
Status in neutron:
  In Progress

Bug description:
  "TypeError: IPAddress('172.19.0.2') is not JSON serializable" seen on
  gate

  eg. http://logs.openstack.org/51/410451/1/check/gate-tempest-dsvm-
  networking-midonet-ml2-ubuntu-
  xenial/b810ef8/logs/screen-q-svc.txt.gz#_2016-12-13_23_29_12_286

  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
[req-b4c0541f-8e87-4539-a8ad-c4a2b10098cf admin -] update failed: No details.
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource Traceback (most 
recent call last):
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource result = 
method(request=request, **args)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 612, in update
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
self._update(request, id, body, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 92, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource setattr(e, 
'_RETRY_EXCEEDED', True)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 88, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*args, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 151, in wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource ectxt.value = 
e.inner_exc
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 139, in wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*args, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 128, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
traceback.format_exc())
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
self.force_reraise()
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource 
six.reraise(self.type_, self.value, self.tb)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 123, in wrapped
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
f(*dup_args, **dup_kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 660, in _update
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource obj = 
obj_updater(request.context, id, **kwargs)
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource   File 
"/usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py", line 48, in 
wrapper
  2016-12-13 23:29:12.286 23652 ERROR neutron.api.v2.resource return 
method(*args, **kwargs)
  2016-12-13 

[Yahoo-eng-team] [Bug 1650002] Re: ovs extraroute_db: _make_extra_route_list returns IPAddressField

[Isaku Yamahata]

This is duplicated with
https://bugs.launchpad.net/networking-odl/+bug/1649733

Mark this as invalid.


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

** Changed in: networking-odl
   Status: New => Invalid

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

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

Title:
  ovs extraroute_db: _make_extra_route_list returns IPAddressField

Status in networking-odl:
  Invalid
Status in neutron:
  Invalid

Bug description:
  ExtraRoute_dbonly_mixin._make_extra_route_list returns IPNetworkField,
  not string.

  It should return {"nexthop": string, "destination": string}, but it returns 
IPNetworkField.
  As a result it breaks networking-odl.
  https://bugs.launchpad.net/networking-odl/+bug/1649993

  The culprit is https://review.openstack.org/#/c/367071/

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1650002/+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 1650002] [NEW] ovs extraroute_db: _make_extra_route_list returns IPAddressField

[Isaku Yamahata]

Public bug reported:

ExtraRoute_dbonly_mixin._make_extra_route_list returns IPNetworkField,
not string.

It should return {"nexthop": string, "destination": string}, but it returns 
IPNetworkField.
As a result it breaks networking-odl.
https://bugs.launchpad.net/networking-odl/+bug/1649993

The culprit is https://review.openstack.org/#/c/367071/

** Affects: networking-odl
 Importance: Critical
 Status: New

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: In Progress

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
   Importance: Undecided => Critical

** Description changed:

  ExtraRoute_dbonly_mixin._make_extra_route_list returns IPNetworkField,
  not string.
  
  It should return {"nexthop": string, "destination": string}, but it returns 
IPNetworkField.
  As a result it breaks networking-odl.
  https://bugs.launchpad.net/networking-odl/+bug/1649993
+ 
+ The culprit is https://review.openstack.org/#/c/367071/

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

Title:
  ovs extraroute_db: _make_extra_route_list returns IPAddressField

Status in networking-odl:
  New
Status in neutron:
  In Progress

Bug description:
  ExtraRoute_dbonly_mixin._make_extra_route_list returns IPNetworkField,
  not string.

  It should return {"nexthop": string, "destination": string}, but it returns 
IPNetworkField.
  As a result it breaks networking-odl.
  https://bugs.launchpad.net/networking-odl/+bug/1649993

  The culprit is https://review.openstack.org/#/c/367071/

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1650002/+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 1470615] Re: retry decorator mask underlying exceptions

[Isaku Yamahata]

** Changed in: networking-odl
   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/1470615

Title:
  retry decorator mask underlying exceptions

Status in networking-odl:
  Fix Released
Status in networking-ovn:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  message:"Unrecognized attribute(s) 'network:tenant_id'"

  
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVW5yZWNvZ25pemVkIGF0dHJpYnV0ZShzKSAnbmV0d29yazp0ZW5hbnRfaWQnXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzU3NzUxNjIyMDR9

  message:"EncodeError: Circular reference detected"

  
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRW5jb2RlRXJyb3I6IENpcmN1bGFyIHJlZmVyZW5jZSBkZXRlY3RlZFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDM1Nzc1MjE2MTk4fQ==

  Trace examples:

  http://logs.openstack.org/03/192003/9/check/check-tempest-dsvm-
  networking-odl/8f05ff0/logs/screen-q-svc.txt.gz?level=TRACE

  Culprit:

  https://review.openstack.org/#/c/191540

  Analysis:

  When we retry on deadlock, we do so by passing a resource that's being
  mutated, hence containing a bunch of stuff that comes from policy
  engine, post-api processing...and that causes all sorts of problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1470615/+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 1550278] Re: tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.* tempest tests are failing repeatedly in the gate for networking-ovn

[Isaku Yamahata]

This happends repeatedly to networking-odl too.
The issue is that update_port on dhcp port raises PortNotFound.
But the dhcp port isn't created by agent yet.


** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
   Importance: Undecided => Critical

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

Title:
  tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.* tempest tests
  are failing repeatedly in the gate for networking-ovn

Status in networking-odl:
  New
Status in networking-ovn:
  Fix Released
Status in neutron:
  Incomplete

Bug description:
  We are seeing a lot of tempest failures for the tests 
tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.* 
  with the below error.

  Either we should fix the error or at least disable these tests
  temporarily.

  
  t156.9: 
tempest.api.network.test_dhcp_ipv6.NetworksTestDHCPv6.test_dhcpv6_stateless_no_ra[id-ae2f4a5d-03ff-4c42-a3b0-ce2fcb7ea832]_StringException:
 Empty attachments:
stderr
stdout

  pythonlogging:'': {{{
  2016-02-26 07:29:46,168 4673 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:test_dhcpv6_stateless_no_ra): 404 POST 
http://127.0.0.1:9696/v2.0/subnets 0.370s
  2016-02-26 07:29:46,169 4673 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: {"subnet": {"cidr": "2003::/64", "ip_version": 6, "network_id": 
"4c7de56a-b059-4239-a5a0-94a53ba4929c", "gateway_ip": "2003::1", 
"ipv6_address_mode": "slaac"}}
  Response - Headers: {'content-length': '132', 'status': '404', 'date': 
'Fri, 26 Feb 2016 07:29:46 GMT', 'connection': 'close', 'content-type': 
'application/json; charset=UTF-8', 'x-openstack-request-id': 
'req-e21f771f-1a16-452a-9429-8a01f0409ae3'}
  Body: {"NeutronError": {"message": "Port 
598c23eb-1ae4-4010-a263-39f86240fd86 could not be found.", "type": 
"PortNotFound", "detail": ""}}
  2016-02-26 07:29:46,196 4673 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:tearDown): 200 GET http://127.0.0.1:9696/v2.0/ports 
0.024s
  2016-02-26 07:29:46,197 4673 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'content-location': 
'http://127.0.0.1:9696/v2.0/ports', 'content-length': '13', 'status': '200', 
'date': 'Fri, 26 Feb 2016 07:29:46 GMT', 'connection': 'close', 'content-type': 
'application/json; charset=UTF-8', 'x-openstack-request-id': 
'req-f0966c23-c72f-4a6f-b113-5d88a6dd5912'}
  Body: {"ports": []}
  2016-02-26 07:29:46,250 4673 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:tearDown): 200 GET 
http://127.0.0.1:9696/v2.0/subnets 0.052s
  2016-02-26 07:29:46,251 4673 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'content-location': 
'http://127.0.0.1:9696/v2.0/subnets', 'content-length': '457', 'status': '200', 
'date': 'Fri, 26 Feb 2016 07:29:46 GMT', 'connection': 'close', 'content-type': 
'application/json; charset=UTF-8', 'x-openstack-request-id': 
'req-3b29ba53-9ae0-4c0f-8c18-ec12db7a6bde'}
  Body: {"subnets": [{"name": "", "enable_dhcp": true, "network_id": 
"4c7de56a-b059-4239-a5a0-94a53ba4929c", "tenant_id": 
"631f9cb1391d41b6aba109afe06bc51b", "dns_nameservers": [], "gateway_ip": 
"2003::1", "ipv6_ra_mode": null, "allocation_pools": [{"start": "2003::2", 
"end": "2003:::::"}], "host_routes": [], "ip_version": 6, 
"ipv6_address_mode": "slaac", "cidr": "2003::/64", "id": 
"6bc2602c-2584-44cc-a6cd-b8af444f6403", "subnetpool_id": null}]}
  2016-02-26 07:29:46,293 4673 INFO [tempest.lib.common.rest_client] 
Request (NetworksTestDHCPv6:tearDown): 200 GET 
http://127.0.0.1:9696/v2.0/routers 0.041s
  2016-02-26 07:29:46,293 4673 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Content-Type': 'application/json', 'Accept': 
'application/json', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'content-location': 
'http://127.0.0.1:9696/v2.0/routers', 'content-length': '15', 'status': '200', 
'date': 'Fri, 26 Feb 2016 07:29:46 GMT', 'connection': 'close', 'content-type': 
'application/json; charset=UTF-8', 'x-openstack-request-id': 
'req-2b883ce9-b10f-4a49-a854-450c341f9cd9'}
  Body: {"routers": []}
  }}}

  Traceback (most recent call last):
File "tempest/api/network/test_dhcp_ipv6.py", line 129, in 
test_dhcpv6_stateless_no_ra
  real_ip, eui_ip = self._get_ips_from_subnet(**kwargs)
File "tempest/api/network/test_dhcp_ipv6.py", line 91, in 
_get_ips_from_subnet
  subnet = 

[Yahoo-eng-team] [Bug 1627044] Re: Last chance call to neutron if VIF plugin notification is lost

[Isaku Yamahata]

** Also 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/1627044

Title:
  Last chance call to neutron if VIF plugin notification is lost

Status in neutron:
  New
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  While spawning a new VM, Nova waits for event from Neutron that its
  port is configured. In some cases Neutron event is lost (e.g. RabbitMQ
  issue) and if vif_plugging_is_fatal=True (it is by default) the
  instance is set to ERROR state. It happens even if in fact port is
  ACTIVE on Neutron side and all should work fine.

  This workflow could be improved by calling Neutron before failing.
  Nova could check real state of each port in Neutron just before setting the 
instance in ERROR (if at least one port is not ACTIVE).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1627044/+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 1641813] [NEW] stable/newton branch creation request for networking-odl

[Isaku Yamahata]

Public bug reported:

Please create stable/newton branch of networking-odl on
f313b7f5b3ebba5bd6f7e8e855315e1570c71f54

the corresponding patch for openstack/release can be found at
https://review.openstack.org/#/c/395415/

** Affects: networking-odl
 Importance: High
 Assignee: Isaku Yamahata (yamahata)
 Status: New

** Affects: neutron
 Importance: Undecided
 Status: New

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

** Changed in: networking-odl
   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/1641813

Title:
  stable/newton branch creation request for networking-odl

Status in networking-odl:
  New
Status in neutron:
  New

Bug description:
  Please create stable/newton branch of networking-odl on
  f313b7f5b3ebba5bd6f7e8e855315e1570c71f54

  the corresponding patch for openstack/release can be found at
  https://review.openstack.org/#/c/395415/

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1641813/+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 1639539] [NEW] security group/security group rule bulk creation is broken

[Isaku Yamahata]

Public bug reported:

security group/security group rule bulk creation is (potentially)
broken.

neutron/db/securitygroups_db.SecurityGroupDbMixin.create_security_group[_rule]_bluk
calls _create_bulk which calls create_security_group[_rule]() within db 
transaction.
This implentation isn't correct because create_security_group[_rule] calls 
AFTER_CRATE callback
which shouldn't be called within db transaction.

The solution is to implement its own bulk create operation like 
neutron.plugins.ml2.plugin.Ml2Plugin._create_bluk_ml2
which knows about precommit/postcommit.

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

Title:
  security group/security group rule bulk creation is broken

Status in neutron:
  New

Bug description:
  security group/security group rule bulk creation is (potentially)
  broken.

  
neutron/db/securitygroups_db.SecurityGroupDbMixin.create_security_group[_rule]_bluk
  calls _create_bulk which calls create_security_group[_rule]() within db 
transaction.
  This implentation isn't correct because create_security_group[_rule] calls 
AFTER_CRATE callback
  which shouldn't be called within db transaction.

  The solution is to implement its own bulk create operation like 
neutron.plugins.ml2.plugin.Ml2Plugin._create_bluk_ml2
  which knows about precommit/postcommit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1639539/+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 1618601] [NEW] test_update_port_status_notify_port_event_after_update fails

[Isaku Yamahata]

Public bug reported:

test_update_port_status_notify_port_event_after_update fails to break
gate job

https://review.openstack.org/#/c/357458/
The change set of 25f5912cf8f69f18d111bd60a6cc6ee488755ff3
change id of Iedad1ccae45005efaaa74d5571df04197757d07a
introduced a test test_update_port_status_notify_port_event_after_update
that is valid only when l3 plugin support l3-ha.

The test shouldn't run when l3-ha isn't supported.

** Affects: networking-odl
 Importance: Critical
 Assignee: Isaku Yamahata (yamahata)
 Status: Invalid

** Affects: neutron
 Importance: Undecided
 Status: New

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

** Changed in: networking-odl
   Importance: Undecided => Critical

** Changed in: networking-odl
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

** Changed in: networking-odl
   Status: New => Invalid

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

Title:
  test_update_port_status_notify_port_event_after_update fails

Status in networking-odl:
  Invalid
Status in neutron:
  New

Bug description:
  test_update_port_status_notify_port_event_after_update fails to break
  gate job

  https://review.openstack.org/#/c/357458/
  The change set of 25f5912cf8f69f18d111bd60a6cc6ee488755ff3
  change id of Iedad1ccae45005efaaa74d5571df04197757d07a
  introduced a test test_update_port_status_notify_port_event_after_update
  that is valid only when l3 plugin support l3-ha.

  The test shouldn't run when l3-ha isn't supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1618601/+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 1616547] [NEW] qos: rule api definition shouldn't include tenant_id

[Isaku Yamahata]

Public bug reported:

QoS rule doesn't have tenant_id accroding to db model and ovo object.
On the other hand, neutron/extension/qos.py defines tenant_id in rule.

the changeset of 4ee9eebd7dd5ed7c87d481eda500b664ae564644 and the change id of 
If9c7a7b9b8a5d2367d8f3225fbf07d8e3ec8865d
introduced it. But it seems accidental.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1616547

Title:
  qos: rule api definition shouldn't include tenant_id

Status in neutron:
  In Progress

Bug description:
  QoS rule doesn't have tenant_id accroding to db model and ovo object.
  On the other hand, neutron/extension/qos.py defines tenant_id in rule.

  the changeset of 4ee9eebd7dd5ed7c87d481eda500b664ae564644 and the change id 
of If9c7a7b9b8a5d2367d8f3225fbf07d8e3ec8865d
  introduced it. But it seems accidental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616547/+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 1546422] Re: secgroup in v1 driver could not work in lithium

[Isaku Yamahata]

ODL Lithium release isn't planned any more as
https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan.

If there is issue with later version of ODL, please open another report.


** Changed in: networking-odl
   Status: New => Won't Fix

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

Title:
  secgroup in v1 driver could not work in lithium

Status in networking-odl:
  Won't Fix
Status in neutron:
  Won't Fix

Bug description:
  Can not reproduce it in beryllium-rc3.1

  why CI not find it:
  sync_from_callback will reraise the error return from sendjson, but because 
notify in ./neutron/callbacks/manager.py ingnored this error(just work on 
BEFORE/PRECOMMIT), so no error will be returned to user like tempest test case.

  I think we need update the neutron code and also find the real reason
  in opendaylight/networking-odl.

  how to reproduce:
  #neutron security-group-create abc

  log in q-svc.log
  2016-02-17 07:33:32.570 DEBUG networking_odl.common.client 
[req-22d86d88-429e-4ad0-ae28-9a581f1c490f tempest-SecGroupIPv6Test-800897536 
5b9a2d254b9c4891ad0b280877acafcf] Exception from ODL: 500 Server Error: Server 
Error for url: 
http://192.168.2.159:8087/controller/nb/v2/neutron/security-groups 
  
  
  Error 500 Server Error
  
  HTTP ERROR 500
  Problem accessing /controller/nb/v2/neutron/security-groups. Reason:
  Server ErrorCaused 
by:java.lang.NullPointerException
  at 
java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333)
  at 
java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:1016)
  at 
org.opendaylight.neutron.transcriber.NeutronSecurityGroupInterface.neutronSecurityGroupExists(NeutronSecurityGroupInterface.java:75)
  at 
org.opendaylight.neutron.transcriber.NeutronSecurityGroupInterface.getNeutronSecurityGroup(NeutronSecurityGroupInterface.java:80)
  at 
org.opendaylight.neutron.transcriber.NeutronSecurityRuleInterface.updateSecGroupRuleInSecurityGroup(NeutronSecurityRuleInterface.java:75)
  at 
org.opendaylight.neutron.transcriber.NeutronSecurityRuleInterface.addNeutronSecurityRule(NeutronSecurityRuleInterface.java:136)
  at 
org.opendaylight.neutron.transcriber.NeutronSecurityGroupInterface.addNeutronSecurityGroup(NeutronSecurityGroupInterface.java:107)
  at 
org.opendaylight.neutron.northbound.api.NeutronSecurityGroupsNorthbound.createSecurityGroups(NeutronSecurityGroupsNorthbound.java:203)
  at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
  at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
  at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
  at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
  at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
  at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
  at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
  at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1511)
  at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1442)
  at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1391)
  at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1381)
  at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
  at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
  at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
  at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
  at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
  at 
org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:247)
  at 
org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:210)
  at 

[Yahoo-eng-team] [Bug 1614766] [NEW] ovsdb managers shouldn't bbe erased/overwritten

[Isaku Yamahata]

Public bug reported:

neutron(ovs or dhcp) agent with native ovslib sets to its own ovsdb
managers.

In some use cases, cloud admin sets ovsdb managers. e.g. monitoring/debug 
purses, sdn controller.
neutron agents shouldn't erase those settings.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1614766

Title:
  ovsdb managers shouldn't bbe erased/overwritten

Status in neutron:
  In Progress

Bug description:
  neutron(ovs or dhcp) agent with native ovslib sets to its own ovsdb
  managers.

  In some use cases, cloud admin sets ovsdb managers. e.g. monitoring/debug 
purses, sdn controller.
  neutron agents shouldn't erase those settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1614766/+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 1614728] [NEW] qos: rule list in policy is too difficult to use

[Isaku Yamahata]

Public bug reported:

The format of qos policy should be something like
{"policy": {"rules": {"bandwidth_limit": {...}, "dscp_marking": {...

https://review.openstack.org/#/c/207043/
The patch changed the format of qos policy to something like this
{"rules": [{"type": "bandwitdh_limit", ...}, {"type": "dscp_marking", ...}, ]}
with the rationale that there should be zero-or-one rule per each rule-type.

But the format has the following issues
- there is no guarantee that there is at most one rule per rule-type
  In order to verify that, the list has to be scanned.
- When agent(or backend) programs switch for specific rule-type,
  it has to scan the list to find a rule of a give rule-type
- the format is unfriendly to parser or external tools.(In my case java jaxb)
  The actual variable type of rule needs to be determined by reading ahead
  "type". Then the rule needs to be parsed again.

So the following format is better
{"rules": {"bandwidth_limit": {...}, "dscp_marking": {...}}}
- it is guaranteed that there is zero-or-one rule per rule-type
- it's easy to find a rule of a given rule-type
- parser easily determine variable-type.

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

Title:
  qos: rule list in policy is too difficult to use

Status in neutron:
  New

Bug description:
  The format of qos policy should be something like
  {"policy": {"rules": {"bandwidth_limit": {...}, "dscp_marking": {...

  https://review.openstack.org/#/c/207043/
  The patch changed the format of qos policy to something like this
  {"rules": [{"type": "bandwitdh_limit", ...}, {"type": "dscp_marking", ...}, ]}
  with the rationale that there should be zero-or-one rule per each rule-type.

  But the format has the following issues
  - there is no guarantee that there is at most one rule per rule-type
In order to verify that, the list has to be scanned.
  - When agent(or backend) programs switch for specific rule-type,
it has to scan the list to find a rule of a give rule-type
  - the format is unfriendly to parser or external tools.(In my case java jaxb)
The actual variable type of rule needs to be determined by reading ahead
"type". Then the rule needs to be parsed again.

  So the following format is better
  {"rules": {"bandwidth_limit": {...}, "dscp_marking": {...}}}
  - it is guaranteed that there is zero-or-one rule per rule-type
  - it's easy to find a rule of a given rule-type
  - parser easily determine variable-type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1614728/+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 1546910] Re: args pass to securitygroup precommit event should include the complete info

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
   Importance: Undecided => High

** Changed in: networking-odl
   Status: New => In Progress

** Changed in: networking-odl
 Assignee: (unassigned) => Manjeet Singh Bhatia (manjeet-s-bhatia)

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

Title:
  args pass to securitygroup precommit event should include the complete
  info

Status in networking-odl:
  In Progress
Status in neutron:
  In Progress

Bug description:
  We introduced the PRECOMMIT_XXX event, but in securitygroups_db.py,
  the kwargs passed to it do not include the complete info of DB like
  AFTER_XXX event. For example, the id of the new created sg/rule.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1546910/+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 1609184] [NEW] [RFE] ML2: Allow retry on db error by precommit

[Isaku Yamahata]

Public bug reported:

Allow retry on db retriable error by precommit mothod.

Currently ML2 driver manager swallows all exceptions by mechanism driver and 
return errors to user.
However, there are classes of retriable db errors(DBDeadlock, taleDataError, 
DDuplicateEntry, TretryRequest).
With those error by precommit, it's better to allow 
neutron.api.v2.base.Controller to retry request.

Sometimes, those db error by precommit is inevitable. Especially subnet
operation touches many resources(port, ip address, etc).

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: New


** Tags: ml2 rfe

** Tags added: rfe

** Tags added: ml2

** Changed in: neutron
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

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

Title:
  [RFE] ML2: Allow retry on db error by precommit

Status in neutron:
  New

Bug description:
  Allow retry on db retriable error by precommit mothod.

  Currently ML2 driver manager swallows all exceptions by mechanism driver and 
return errors to user.
  However, there are classes of retriable db errors(DBDeadlock, taleDataError, 
DDuplicateEntry, TretryRequest).
  With those error by precommit, it's better to allow 
neutron.api.v2.base.Controller to retry request.

  Sometimes, those db error by precommit is inevitable. Especially
  subnet operation touches many resources(port, ip address, etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1609184/+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 1607979] [NEW] many tests directly modify RESOURCE_ATTRIBUTES_MAP

[Isaku Yamahata]

Public bug reported:

many tests directly modify the global variable, RESOURCE_ATTRIBUTES_MAP
and leave it modified.

As a result, the value isn't predictable. So the test result can be 
non-deterministic depending on the execution order.
Especially the result can be different when only the test is run and when it's 
run as whole.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1607979

Title:
  many tests directly modify RESOURCE_ATTRIBUTES_MAP

Status in neutron:
  In Progress

Bug description:
  many tests directly modify the global variable,
  RESOURCE_ATTRIBUTES_MAP and leave it modified.

  As a result, the value isn't predictable. So the test result can be 
non-deterministic depending on the execution order.
  Especially the result can be different when only the test is run and when 
it's run as whole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1607979/+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 1603235] [NEW] trunk plugin missing necessary callback

[Isaku Yamahata]

Public bug reported:

trunk pluin now provides only notification on add/delete_subports.
For SDN controller support(OpenDaylight specifically) more callbacks are needed.
https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms

- resource: TRUNK event: PRECOMMIT/AFTER_CREATE/DELETE on trunk creaion/deletion
- resource:TRUNK event: PRECOMMIT/AFTER_UPDATE on add/delete subports

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1603235

Title:
  trunk plugin missing necessary callback

Status in neutron:
  In Progress

Bug description:
  trunk pluin now provides only notification on add/delete_subports.
  For SDN controller support(OpenDaylight specifically) more callbacks are 
needed.
  https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms

  - resource: TRUNK event: PRECOMMIT/AFTER_CREATE/DELETE on trunk 
creaion/deletion
  - resource:TRUNK event: PRECOMMIT/AFTER_UPDATE on add/delete subports

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1603235/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1489059] Re: "db type could not be determined" running py34

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

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

** Changed in: networking-odl
   Status: New => In Progress

** Changed in: networking-odl
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Bareon:
  Fix Released
Status in Cinder:
  Fix Released
Status in cloudkitty:
  Fix Released
Status in Fuel for OpenStack:
  In Progress
Status in Fuel for OpenStack mitaka series:
  Won't Fix
Status in Fuel for OpenStack newton series:
  In Progress
Status in Glance:
  Fix Released
Status in hacking:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in kolla:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  Fix Released
Status in neutron:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-muranoclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in python-swiftclient:
  In Progress
Status in Rally:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  Fix Released
Status in senlin:
  Fix Released
Status in tap-as-a-service:
  Fix Released
Status in tempest:
  Fix Released
Status in zaqar:
  Fix Released
Status in python-ironicclient package in Ubuntu:
  Fix Committed

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1545218] Re: TestMl2PortsV2.test_update_port_host_id_changed may fail depending on ML2 driver

[Isaku Yamahata]

** Changed in: networking-odl
   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/1545218

Title:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver

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

Bug description:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver.

  Concretely with ODL ML2 driver, the test fails because it changes port status 
to ACTIVE on port binding.
  The assumption of the test is not always true.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1545218/+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 1545218] [NEW] TestMl2PortsV2.test_update_port_host_id_changed may fail depending on ML2 driver

[Isaku Yamahata]

Public bug reported:

TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
ML2 driver.

Concretely with ODL ML2 driver, the test fails because it changes port status 
to ACTIVE on port binding.
The assumption of the test is not always true.

** Affects: networking-odl
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: New

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: In Progress

** Changed in: neutron
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

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

Title:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver

Status in networking-odl:
  New
Status in neutron:
  In Progress

Bug description:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver.

  Concretely with ODL ML2 driver, the test fails because it changes port status 
to ACTIVE on port binding.
  The assumption of the test is not always true.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1545218/+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 1545218] Re: TestMl2PortsV2.test_update_port_host_id_changed may fail depending on ML2 driver

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
 Assignee: (unassigned) => Isaku Yamahata (yamahata)

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

Title:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver

Status in networking-odl:
  New
Status in neutron:
  In Progress

Bug description:
  TestMl2PortsV2.test_update_port_host_id_changed may fail depending on
  ML2 driver.

  Concretely with ODL ML2 driver, the test fails because it changes port status 
to ACTIVE on port binding.
  The assumption of the test is not always true.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1545218/+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 1475093] [NEW] l3_db updates port db without calling l2 plugin

[Isaku Yamahata]

Public bug reported:

l3 db updates port::owner directly without calling l2 plugin when adding an 
interface to the router.
So ML2 mechanism driver gets confused resulting an error.

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

Title:
  l3_db updates port db without calling l2 plugin

Status in neutron:
  New

Bug description:
  l3 db updates port::owner directly without calling l2 plugin when adding an 
interface to the router.
  So ML2 mechanism driver gets confused resulting an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1475093/+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 1474265] [NEW] ml2 triggers attribute error for dvr_deletens_if_no_port

[Isaku Yamahata]

Public bug reported:

When using odl mechanism driver and l3 odl plugin, the following
exception occurs

2015-07-13 19:09:22.568 ERROR oslo_messaging.rpc.dispatcher 
[req-e9a7622a-b904-4c43-9c17-2914a7f45963 None None] Exception during message 
handling: 'OpenDaylightL3RouterPlug
in' object has no attribute 'dvr_deletens_if_no_port'
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
142, in _dispatch_and_repl
y
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
186, in _dispatch
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
130, in _do_dispatch
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/api/rpc/handlers/dhcp_rpc.py, line 170, in 
release_dhcp_por
t
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
plugin.delete_ports_by_device_id(context, device_id, network_id)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/db/db_base_plugin_v2.py, line 884, in 
delete_ports_by_devic
e_id
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
self.delete_port(context, port_id)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py, line 146, in wrapper
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher ectxt.value = 
e.inner_exc
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 119, in 
__exit__
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py, line 136, in wrapper
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher return f(*args, 
**kwargs)
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/plugins/ml2/plugin.py, line 1291, in delete_port
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher removed_routers 
= l3plugin.dvr_deletens_if_no_port(
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher AttributeError: 
'OpenDaylightL3RouterPlugin' object has no attribute 'dvr_deletens_if_no_port'
2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher

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

Title:
  ml2 triggers attribute error for dvr_deletens_if_no_port

Status in neutron:
  New

Bug description:
  When using odl mechanism driver and l3 odl plugin, the following
  exception occurs

  2015-07-13 19:09:22.568 ERROR oslo_messaging.rpc.dispatcher 
[req-e9a7622a-b904-4c43-9c17-2914a7f45963 None None] Exception during message 
handling: 'OpenDaylightL3RouterPlug
  in' object has no attribute 'dvr_deletens_if_no_port'
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
142, in _dispatch_and_repl
  y
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
186, in _dispatch
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
130, in _do_dispatch
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/api/rpc/handlers/dhcp_rpc.py, line 170, in 
release_dhcp_por
  t
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
plugin.delete_ports_by_device_id(context, device_id, network_id)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/db/db_base_plugin_v2.py, line 884, in 
delete_ports_by_devic
  e_id
  2015-07-13 19:09:22.568 TRACE 

[Yahoo-eng-team] [Bug 1474265] Re: ml2 triggers attribute error for dvr_deletens_if_no_port

[Isaku Yamahata]

** Also affects: networking-odl
   Importance: Undecided
   Status: New

** Changed in: networking-odl
 Assignee: (unassigned) = Isaku Yamahata (yamahata)

** No longer affects: neutron

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

Title:
  ml2 triggers attribute error for dvr_deletens_if_no_port

Status in networking-odl:
  New

Bug description:
  When using odl mechanism driver and l3 odl plugin, the following
  exception occurs

  2015-07-13 19:09:22.568 ERROR oslo_messaging.rpc.dispatcher 
[req-e9a7622a-b904-4c43-9c17-2914a7f45963 None None] Exception during message 
handling: 'OpenDaylightL3RouterPlug
  in' object has no attribute 'dvr_deletens_if_no_port'
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
142, in _dispatch_and_repl
  y
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
186, in _dispatch
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py, line 
130, in _do_dispatch
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/api/rpc/handlers/dhcp_rpc.py, line 170, in 
release_dhcp_por
  t
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
plugin.delete_ports_by_device_id(context, device_id, network_id)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/db/db_base_plugin_v2.py, line 884, in 
delete_ports_by_devic
  e_id
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
self.delete_port(context, port_id)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py, line 146, in wrapper
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher ectxt.value = 
e.inner_exc
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py, line 119, in 
__exit__
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo_db/api.py, line 136, in wrapper
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher return 
f(*args, **kwargs)
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher   File 
/odl/neutron/neutron/plugins/ml2/plugin.py, line 1291, in delete_port
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher 
removed_routers = l3plugin.dvr_deletens_if_no_port(
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher AttributeError: 
'OpenDaylightL3RouterPlugin' object has no attribute 'dvr_deletens_if_no_port'
  2015-07-13 19:09:22.568 TRACE oslo_messaging.rpc.dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1474265/+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 1464806] [NEW] tenant_id is set to ''(empty string) by l3 plugin

[Isaku Yamahata]

Public bug reported:

L3 plugin code (neutorn/db/l3_*_db.py) calls l2 plugin with tenant_id=''(empty 
string) for creation port and subnet for internal use.
e.g. gateway port, floating ip port, port used by dvr.

This is ugly hack and some L2 plugin or ML2 mechanism driver doesn't expect it 
and be confused with it.
It is better to fix it.

tenant_id=''(empty string) is used for those purpose.
- prevent (non-admin) user from updating
  NeutronDbPluginV2._enforce_device_owner_not_router_intf_or_device_id
- prevent (non-admin) user from deleting
 NeutronDbPluginV2 ._delete_port
- don't count for quota
  Controller.create

This dirty hack was firstly introduced by
the changeset of a7326a947bc0b30778e06acd772dd38bcb28d96d
the change id of Ice72fc6d3b1c613d596c037818ed66d7e9ed841d
with only one line comment. The followers just use it without any

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

Title:
  tenant_id is set to ''(empty string) by l3 plugin

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  L3 plugin code (neutorn/db/l3_*_db.py) calls l2 plugin with 
tenant_id=''(empty string) for creation port and subnet for internal use.
  e.g. gateway port, floating ip port, port used by dvr.

  This is ugly hack and some L2 plugin or ML2 mechanism driver doesn't expect 
it and be confused with it.
  It is better to fix it.

  tenant_id=''(empty string) is used for those purpose.
  - prevent (non-admin) user from updating
NeutronDbPluginV2._enforce_device_owner_not_router_intf_or_device_id
  - prevent (non-admin) user from deleting
   NeutronDbPluginV2 ._delete_port
  - don't count for quota
Controller.create

  This dirty hack was firstly introduced by
  the changeset of a7326a947bc0b30778e06acd772dd38bcb28d96d
  the change id of Ice72fc6d3b1c613d596c037818ed66d7e9ed841d
  with only one line comment. The followers just use it without any

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1464806/+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 1454385] Re: can't boot vm instance on network with port_security_enabled=False

[Isaku Yamahata]

This is because subnet is missing.
After creating subnet, vm booted.


** Changed in: nova
   Status: New = Invalid

** Changed in: neutron
   Status: New = Invalid

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

Title:
  can't boot vm instance on network with port_security_enabled=False

Status in OpenStack Neutron (virtual network service):
  Invalid
Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  $ neutron net-create --port_security_enabled=False test-net 
  Created a new network:
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | id| 4811c94c-f7db-49bf-86c6-6aa270e79b3c |
  | mtu   | 0|
  | name  | test-net |
  | port_security_enabled | False|
  | provider:network_type | vxlan|
  | provider:physical_network |  |
  | provider:segmentation_id  | 1003 |
  | router:external   | False|
  | shared| False|
  | status| ACTIVE   |
  | subnets   |  |
  | tenant_id | dad7ba3715264009b90176bd29c779c2 |
  | vlan_transparent  | False|
  +---+--+
  $ nova boot --nic net-id=4811c94c-f7db-49bf-86c6-6aa270e79b3c --flavor 
m1.micro --image cirros-0.3.2-x86_64-uec net-test-vm
  ERROR (BadRequest): Network 4811c94c-f7db-49bf-86c6-6aa270e79b3c requires a 
subnet in order to boot instances on. (HTTP 400) (Request-ID: 
req-233d9113-96ae-49bd-abfe-e2f29350af1f)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1454385/+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 1454385] [NEW] can't boot vm instance on network with port_security_enabled=False

[Isaku Yamahata]

Public bug reported:

$ neutron net-create --port_security_enabled=False test-net 
Created a new network:
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| 4811c94c-f7db-49bf-86c6-6aa270e79b3c |
| mtu   | 0|
| name  | test-net |
| port_security_enabled | False|
| provider:network_type | vxlan|
| provider:physical_network |  |
| provider:segmentation_id  | 1003 |
| router:external   | False|
| shared| False|
| status| ACTIVE   |
| subnets   |  |
| tenant_id | dad7ba3715264009b90176bd29c779c2 |
| vlan_transparent  | False|
+---+--+
$ nova boot --nic net-id=4811c94c-f7db-49bf-86c6-6aa270e79b3c --flavor m1.micro 
--image cirros-0.3.2-x86_64-uec net-test-vm
ERROR (BadRequest): Network 4811c94c-f7db-49bf-86c6-6aa270e79b3c requires a 
subnet in order to boot instances on. (HTTP 400) (Request-ID: 
req-233d9113-96ae-49bd-abfe-e2f29350af1f)

** Affects: neutron
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Also affects: nova
   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/1454385

Title:
  can't boot vm instance on network with port_security_enabled=False

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  $ neutron net-create --port_security_enabled=False test-net 
  Created a new network:
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | id| 4811c94c-f7db-49bf-86c6-6aa270e79b3c |
  | mtu   | 0|
  | name  | test-net |
  | port_security_enabled | False|
  | provider:network_type | vxlan|
  | provider:physical_network |  |
  | provider:segmentation_id  | 1003 |
  | router:external   | False|
  | shared| False|
  | status| ACTIVE   |
  | subnets   |  |
  | tenant_id | dad7ba3715264009b90176bd29c779c2 |
  | vlan_transparent  | False|
  +---+--+
  $ nova boot --nic net-id=4811c94c-f7db-49bf-86c6-6aa270e79b3c --flavor 
m1.micro --image cirros-0.3.2-x86_64-uec net-test-vm
  ERROR (BadRequest): Network 4811c94c-f7db-49bf-86c6-6aa270e79b3c requires a 
subnet in order to boot instances on. (HTTP 400) (Request-ID: 
req-233d9113-96ae-49bd-abfe-e2f29350af1f)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1454385/+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 1431096] [NEW] pylint: Using type() instead of isinstance() for a typecheck. (unidiomatic-typecheck)

[Isaku Yamahata]

Public bug reported:

pylint raises false positive warning as follows from version 1.4.2.

 * Module neutron.agent.l3.event_observers
 W: 27,15: Using type() instead of isinstance() for a typecheck. 
 (unidiomatic-typecheck)

** Affects: neutron
 Importance: Undecided
 Status: Invalid

** Changed in: neutron
   Status: New = Invalid

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

Title:
  pylint: Using type() instead of isinstance() for a typecheck.
  (unidiomatic-typecheck)

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  pylint raises false positive warning as follows from version 1.4.2.

   * Module neutron.agent.l3.event_observers
   W: 27,15: Using type() instead of isinstance() for a typecheck. 
(unidiomatic-typecheck)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1431096/+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 1418196] [NEW] fwaas: driver base class is stale

[Isaku Yamahata]

Public bug reported:

The change set of f69ed3b3,   Change-Id: 
Iba78e534ccf347ea6270aabc939a489dd40a7b9e
updated update_firewall, delete_firewall, it missed to update FwaasDriverBase 
and vArmourFwaasDriver

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

Title:
  fwaas: driver base class is stale

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The change set of f69ed3b3,   Change-Id: 
Iba78e534ccf347ea6270aabc939a489dd40a7b9e
  updated update_firewall, delete_firewall, it missed to update FwaasDriverBase 
and vArmourFwaasDriver

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1418196/+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 1387012] [NEW] pylint isn't listed on tox testenvironment

[Isaku Yamahata]

Public bug reported:

Now pylint test is added to jenkins. But pylint isn't listed in tox test
environments and isn't in test-requirements.

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

Title:
  pylint isn't listed on tox testenvironment

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Now pylint test is added to jenkins. But pylint isn't listed in tox
  test environments and isn't in test-requirements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1387012/+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 1386046] [NEW] test_contrail_plugin.TestContrailL3NatTestCase fakes core plugin very trikerly

[Isaku Yamahata]

Public bug reported:

test_contrail_plugin.TestContrailL3NatTestCase fakes core plugin so
trickery.

It's the way is so trickery that work around for the test to pass is necessary.
The test should be sorted out such that work around should be eliminated.
https://review.openstack.org/#/c/124699/
is the related patches. I hit this issue while I worked on the patch, but this 
is the generic issue.

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

Title:
  test_contrail_plugin.TestContrailL3NatTestCase  fakes core plugin very
  trikerly

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  test_contrail_plugin.TestContrailL3NatTestCase fakes core plugin so
  trickery.

  It's the way is so trickery that work around for the test to pass is 
necessary.
  The test should be sorted out such that work around should be eliminated.
  https://review.openstack.org/#/c/124699/
  is the related patches. I hit this issue while I worked on the patch, but 
this is the generic issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1386046/+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 1386047] [NEW] plugin(core, service) is unnecessarily cached and they are implemented variously by many times

[Isaku Yamahata]

Public bug reported:

There are patterns like

@property
def core_plugin(self):
try:
return self._core_plugin
except AttributeError:
self._core_plugin = manager.NeutronManager.get_plugin()
return self._core_plugin

There are issues.
- NeutronManager.get_plugin already cached it. No need to cache again.
- each class implements its own way(with or without cache), various name.

The caching should be removed and their implementation should be unified

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

Title:
  plugin(core, service) is unnecessarily cached and they are implemented
  variously by many times

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  There are patterns like

  @property
  def core_plugin(self):
  try:
  return self._core_plugin
  except AttributeError:
  self._core_plugin = manager.NeutronManager.get_plugin()
  return self._core_plugin

  There are issues.
  - NeutronManager.get_plugin already cached it. No need to cache again.
  - each class implements its own way(with or without cache), various name.

  The caching should be removed and their implementation should be
  unified

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1386047/+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 1383546] [NEW] direct caller of create_{network, subnet, port} wrongly passed necessary argument

[Isaku Yamahata]

Public bug reported:

The calling convention of plugin create_{network, subnet, port} is all
the necessary argument are filled with default value dynamically. Which
arguments are necessary depends on resource extension which core plugin
supports.

On the other hand, internal direct caller of those methods ignore those
conventions so that adding extension causes exception like key error of
argument.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1383546

Title:
  direct caller of create_{network, subnet, port} wrongly passed
  necessary argument

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  The calling convention of plugin create_{network, subnet, port} is all
  the necessary argument are filled with default value dynamically.
  Which arguments are necessary depends on resource extension which core
  plugin supports.

  On the other hand, internal direct caller of those methods ignore
  those conventions so that adding extension causes exception like key
  error of argument.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1383546/+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 1382360] [NEW] ml2 plugin wrongly calls _filter_nets_l3 from get_networks

[Isaku Yamahata]

Public bug reported:

The commit of 0156ec175cc047826b211727d43d5d14a3e1f2d2, change-id of 
I47e01a11afaf6e6bcf06da7bd713fd39b05600ff which fixes bug 1132849 removed the 
call of _filter_nets_l3 methods.
But the fix missed ml2 plugin somehow.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1382360

Title:
  ml2 plugin wrongly calls _filter_nets_l3 from get_networks

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  The commit of 0156ec175cc047826b211727d43d5d14a3e1f2d2, change-id of 
I47e01a11afaf6e6bcf06da7bd713fd39b05600ff which fixes bug 1132849 removed the 
call of _filter_nets_l3 methods.
  But the fix missed ml2 plugin somehow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1382360/+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 1382448] [NEW] ml2 extension manager doesn't pass db entry to entend_xxx_dict

[Isaku Yamahata]

Public bug reported:

extension driver isn't passed dbentry to extension result dict
extend_{network, subnet, port}_dict() aren't passed db entry, but only result 
dict. In order to extend the result dict, db entry is necessary.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1382448

Title:
  ml2 extension manager doesn't pass db entry to entend_xxx_dict

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  extension driver isn't passed dbentry to extension result dict
  extend_{network, subnet, port}_dict() aren't passed db entry, but only result 
dict. In order to extend the result dict, db entry is necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1382448/+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 1381900] [NEW] l3 agent context name conflict

[Isaku Yamahata]

Public bug reported:

context module imported in l3_agent conflicts with argument name.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1381900

Title:
  l3 agent context name conflict

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  context module imported in l3_agent conflicts with argument name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1381900/+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 1379089] [NEW] get_sync_data is too convoluted

[Isaku Yamahata]

Public bug reported:

l3_db get_sync_data is too convoluted, thus l3_dvr_db fully implements its own 
version.
The method needs to be sort out to be easily extended by its subclass like 
l3_dvr_db

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

Title:
  get_sync_data is too convoluted

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  l3_db get_sync_data is too convoluted, thus l3_dvr_db fully implements its 
own version.
  The method needs to be sort out to be easily extended by its subclass like 
l3_dvr_db

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1379089/+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 1352698] [NEW] neutron context doesn't include auth token

[Isaku Yamahata]

Public bug reported:

Discussed with the thread starting with
http://lists.openstack.org/pipermail/openstack-dev/2014-July/040644.html

Neutron context isn't populated with auth token unlike nova, glance.
Since there are several (potential) users for it. servicevm project, routervm 
implementation(cisco csr1kv, vyatta vrouter),
it makes sense for neutron context to include auth token.

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

Title:
  neutron context doesn't include auth token

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Discussed with the thread starting with
  http://lists.openstack.org/pipermail/openstack-dev/2014-July/040644.html

  Neutron context isn't populated with auth token unlike nova, glance.
  Since there are several (potential) users for it. servicevm project, routervm 
implementation(cisco csr1kv, vyatta vrouter),
  it makes sense for neutron context to include auth token.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1352698/+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 1350252] [NEW] test_l3_plugin fails when run as single test

[Isaku Yamahata]

Public bug reported:

tox  -e py27 neutron.tests.unit.test_l3_plugin
fails as follows. This is bacause necessary oslo config isn't initialized 
properly by L3AgentDbIntTestCase and L3AgentDbSepTestCase

The error log follows.
 $ tox -e py27 neutron.tests.unit.test_l3_plugin
py27 develop-inst-nodeps: 
/home/yamahata/openstack/tacker/neutron-l3-plugin/upstream/neutron-l3-db-refacotr-0
py27 runtests: commands[0] | python -m neutron.openstack.common.lockutils 
python setup.py testr --slowest --testr-args=neutron.tests.unit.test_l3_plugin
running testr
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit} --list
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpNLNI_l
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpBl_vq6
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpO3NkaL
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpc3FrWL
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmppz6MIP
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmprcHfnW
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpVW99Uk
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpMC3U19
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpiqP4jI
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpK6j9JS
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmp_cFhYl
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_LOG_CAPTURE=1 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpNXI0Mi
==
FAIL:
neutron.tests.unit.test_l3_plugin.L3AgentDbSepTestCase.test_l3_agent_routers_query_floatingips
tags: worker-10
--
Traceback (most recent call last):
  File neutron/tests/unit/test_l3_plugin.py, line 2073, in setUp
self.core_plugin = TestNoL3NatPlugin()
  File neutron/db/db_base_plugin_v2.py, line 72, in __init__
db.configure_db()
  File neutron/db/api.py, line 45, in configure_db
register_models()
  File neutron/db/api.py, line 68, in register_models
facade = _create_facade_lazily()
  File neutron/db/api.py, line 34, in _create_facade_lazily
_FACADE = session.EngineFacade.from_config(cfg.CONF, sqlite_fk=True)
  File 
/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo/db/sqlalchemy/session.py,
 line 977, in from_config
retry_interval=conf.database.retry_interval)
  File 
/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo/db/sqlalchemy/session.py,
 line 893, in __init__
**engine_kwargs)
  File 
/neutron/.tox/py27/local/lib/python2.7/site-packages/oslo/db/sqlalchemy/session.py,
 line 650, in create_engine
if sqlite in connection_dict.drivername:
AttributeError: 'NoneType' object has no attribute 'drivername'
==
FAIL: 
neutron.tests.unit.test_l3_plugin.L3AgentDbSepTestCase.test_router_gateway_op_agent
tags: worker-10
--
Traceback (most recent call last):
  File neutron/tests/unit/test_l3_plugin.py, line 2073, in setUp
self.core_plugin = TestNoL3NatPlugin()
  File neutron/db/db_base_plugin_v2.py, line 72, in __init__
db.configure_db()
  File neutron/db/api.py, line 45, in configure_db
register_models()
  File neutron/db/api.py, line 68, in register_models
facade = _create_facade_lazily()
  File neutron/db/api.py, line 34, in _create_facade_lazily
_FACADE = session.EngineFacade.from_config(cfg.CONF, sqlite_fk=True)
  File 

[Yahoo-eng-team] [Bug 1284549] [NEW] tests: notification driver isn't properly cleaned up

[Isaku Yamahata]

Public bug reported:

Some unit tests override notification driver, but doesn't clean it up properly.
So tests can be run against unintended notification driver resulting in error.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1284549

Title:
  tests: notification driver isn't properly cleaned up

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  Some unit tests override notification driver, but doesn't clean it up 
properly.
  So tests can be run against unintended notification driver resulting in error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1284549/+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 1282483] [NEW] lbaas/haproxy/agent: inconsistent periodic_interval option

[Isaku Yamahata]

Public bug reported:

lbaas haproxy agent defines periodic_interval option in DEFAULT group which is 
inconsistent the same option
defined by other agents/servers.
The inconsistency causes a confusion.
Since even major distro document misses this difference, almost all the admins 
can't understand it.

The default value: 10(haproxy) vs 40(others)
behaviour:  neutron.openstack.common.rpc.service.Service.threadgroup(haproxy) 
vs neutron.service.Service(others)

The possible options will be
- make haproxy option same to others
  default value will be changed, behaviour will be changed
- move haproxy option into its own group('haproxy') or rename
- do nothing
- any other?

Anyway the first thing to do is to understand if this difference is necessary 
or not.
the commit log in the change set of f8de8c44 doesn't tell it.

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

Title:
  lbaas/haproxy/agent: inconsistent periodic_interval option

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  lbaas haproxy agent defines periodic_interval option in DEFAULT group which 
is inconsistent the same option
  defined by other agents/servers.
  The inconsistency causes a confusion.
  Since even major distro document misses this difference, almost all the 
admins can't understand it.

  The default value: 10(haproxy) vs 40(others)
  behaviour:  neutron.openstack.common.rpc.service.Service.threadgroup(haproxy) 
vs neutron.service.Service(others)

  The possible options will be
  - make haproxy option same to others
default value will be changed, behaviour will be changed
  - move haproxy option into its own group('haproxy') or rename
  - do nothing
  - any other?

  Anyway the first thing to do is to understand if this difference is necessary 
or not.
  the commit log in the change set of f8de8c44 doesn't tell it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1282483/+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 1279769] [NEW] duplicated config-option registering

[Isaku Yamahata]

Public bug reported:

Some config options(interface_driver, use_namespaces, periodic_interval) are 
defined in multiple sources in ad-hoc way.
It may cause DuplicateOptError exception when using those module at the same 
time.
Right now the exception is avoided in ad-hoc way by each executables.
Those definition/registering should be consolidated.

This is the blocker for BP of l3 agent consolidation.
https://blueprints.launchpad.net/neutron/+spec/l3-agent-consolidation

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) = Isaku Yamahata (yamahata)

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

Title:
  duplicated config-option registering

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Some config options(interface_driver, use_namespaces, periodic_interval) are 
defined in multiple sources in ad-hoc way.
  It may cause DuplicateOptError exception when using those module at the same 
time.
  Right now the exception is avoided in ad-hoc way by each executables.
  Those definition/registering should be consolidated.

  This is the blocker for BP of l3 agent consolidation.
  https://blueprints.launchpad.net/neutron/+spec/l3-agent-consolidation

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1279769/+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 1275654] [NEW] neutron.unit.services code duplication

[Isaku Yamahata]

Public bug reported:

code duplication between 
neutron.unit.services.loadbalancer.test_loadbalancer_plugin
and neutron.unit.services.vpn.test_vpnaas_extension

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

Title:
  neutron.unit.services code duplication

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  code duplication between 
neutron.unit.services.loadbalancer.test_loadbalancer_plugin
  and neutron.unit.services.vpn.test_vpnaas_extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1275654/+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 1261593] Re: tests/ml2: GreTypeTest missing self.addCleanup(db.clear_db)

[Isaku Yamahata]

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

** No longer affects: devstack

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

Title:
  tests/ml2: GreTypeTest missing self.addCleanup(db.clear_db)

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  GreTypeTest.setUp() in test_type_gre.py should have
  self.addCleanup(db.clear_db)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1261593/+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 1260262] [NEW] ml2 gre/vxlan type driver can lose segment_id allocation

[Isaku Yamahata]

Public bug reported:

With ML2 gre/vxlan type driver and multiple segment is specified, the
type driver can leak segment_id

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1260262

Title:
  ml2 gre/vxlan type driver can lose segment_id allocation

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  With ML2 gre/vxlan type driver and multiple segment is specified, the
  type driver can leak segment_id

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1260262/+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 1260598] [NEW] ml2 race in network creation

[Isaku Yamahata]

Public bug reported:

There are races in network create by ML2 type driver.

** Affects: neutron
 Importance: Undecided
 Assignee: Isaku Yamahata (yamahata)
 Status: 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/1260598

Title:
  ml2 race in network creation

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  There are races in network create by ML2 type driver.

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