[Yahoo-eng-team] [Bug 1699500] [NEW] network fetched from DB has deleted subnets in it during db-retry of subnet_create

Public bug reported: Only seen in Newton Possibly related bug: https://bugs.launchpad.net/neutron/+bug/1596075 When a retriable database error occurs in a mechanism driver's subnet_create_postcommit, you get the error saying subnet overlaps with another subnet. What's happening is: 1) mech

[Yahoo-eng-team] [Bug 1699496] [NEW] during get_auto_allocated_topology no extension attributes are send during router-create

Public bug reported: At https://github.com/openstack/neutron/blob/master/neutron/services/auto_allocate/db.py#L307: ** router_args = { 'name': 'auto_allocated_router', l3.EXTERNAL_GW_INFO: {'network_id':

[Yahoo-eng-team] [Bug 1698852] [NEW] port in mechanism driver's create_port_postcommit has no extra_dhcp_opts

Public bug reported: The port in the following code of a mechanism driver will always have extra_dhcp_opts = [], regardless of whether it has dhcp options or not. def create_port_postcommit(self, context): port = context.current port.get('extra_dhcp_opts') # always an empty

[Yahoo-eng-team] [Bug 1687913] [NEW] db retry not triggered when fail happened in after_create notify

Public bug reported: Note: - The specific use case can no longer happen on master (due to a couple of commits). So the below is for a < ocata context. - Bug seen on Newton setup During high concurrency testing (with router:external networks) the following deadlock may occur

[Yahoo-eng-team] [Bug 1657412] [NEW] L3_NAT_dbonly_mixin __new__ method has wrong signature

Public bug reported: Since stable/newton, there is this code: https://github.com/openstack/neutron/blob/stable/newton/neutron/db/l3_db.py#L173 master link: https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L95 Python doc says:

[Yahoo-eng-team] [Bug 1654283] [NEW] test_router_interface_status raises troublesome error when it fails.

Public bug reported: Test: neutron.tests.tempest.api.test_routers#test_router_interface_status This test waits for the router interface port to become active by using neutron.common.utils.wait_until_true. Problem is when it, for whatever reason, would not become active, this test raises an

[Yahoo-eng-team] [Bug 1475093] Re: l3_db updates port db without calling l2 plugin

bgpvpn is also having this issue for https://blueprints.launchpad.net/bgpvpn/+spec/router-bgpvpn-association Inside _add_interface_by_port the port update is happening without using ml2, so there is no way to get notified by this type of router- interface-add. ** Also affects: bgpvpn

[Yahoo-eng-team] [Bug 1498352] [NEW] Traceback when neutron does not support port binding extension in admin screen

Public bug reported: Similar to https://bugs.launchpad.net/horizon/+bug/1477100 In the admin's edit port view, binding:host_id is expected as part of the port object. This gives a traceback when plugins don't use the port binding extension. ... File

[Yahoo-eng-team] [Bug 1461779] [NEW] Nuage plugin is missing configuration

Public bug reported: The nuage_plugin.ini file is missing parameters for the correct functioning of floatingip rate limiting usable in the plugin. ** Affects: neutron Importance: Undecided Assignee: Wim De Clercq (declewi) Status: New ** Changed in: neutron Assignee