[Yahoo-eng-team] [Bug 1931639] [NEW] [OVN Octavia Provider] Load Balancer not reachable from some Subnets
Public bug reported: In situations where router port and load balancer are created back to back, there is a potential race condition that would render OVN with a logical switch that is missing a reference to the load balancer. This issue is also being tracked in Bugzilla, under the link: https://bugzilla.redhat.com/show_bug.cgi?id=1937392 ** Affects: neutron Importance: High Assignee: Flavio Fernandes (ffernand) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) ** Changed in: neutron Importance: Undecided => High ** Changed in: neutron Status: New => In Progress ** Description changed: - - In situations where router port and load balancer are created back to back, - there is a potential race condition that would render OVN with a logical switch - that is missing a reference to the load balancer. - + In situations where router port and load balancer are created back to + back, there is a potential race condition that would render OVN with a + logical switch that is missing a reference to the load balancer. This issue is also being tracked in Bugzilla, under the link: - https://bugzilla.redhat.com/show_bug.cgi?id=1937392 + https://bugzilla.redhat.com/show_bug.cgi?id=1937392 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1931639 Title: [OVN Octavia Provider] Load Balancer not reachable from some Subnets Status in neutron: In Progress Bug description: In situations where router port and load balancer are created back to back, there is a potential race condition that would render OVN with a logical switch that is missing a reference to the load balancer. This issue is also being tracked in Bugzilla, under the link: https://bugzilla.redhat.com/show_bug.cgi?id=1937392 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1931639/+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 1928988] [NEW] [ovn] Disabling SNAT doesn't take effect if the router has already snat enabled
Public bug reported: When we try to disable snat of an existing router, neutron accepts the request and enable_snat is updated but snat rule is not removed form ovn and snat is still available. This bug is being tracked via bugzilla 1962051 For more details, see: https://bugzilla.redhat.com/show_bug.cgi?id=1962051 ** Affects: neutron Importance: Undecided Assignee: Flavio Fernandes (ffernand) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) ** Changed in: neutron Milestone: None => train-3 ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1928988 Title: [ovn] Disabling SNAT doesn't take effect if the router has already snat enabled Status in neutron: In Progress Bug description: When we try to disable snat of an existing router, neutron accepts the request and enable_snat is updated but snat rule is not removed form ovn and snat is still available. This bug is being tracked via bugzilla 1962051 For more details, see: https://bugzilla.redhat.com/show_bug.cgi?id=1962051 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1928988/+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 1926653] [NEW] [ovn] ml2/ovn may time out connecting to ovsdb server and stays dead in the water
Public bug reported: Right now, the IDL connections between ml2/ovn are not resilient enough when connecting. It doesn't make sense to give up on that since the ml2/ovn is useless w/out that access. If ovsdb-server is slow and takes more than timeout seconds, everything reconnecting after partial downloads and starting over is not going to make things better. That is particularly likely to happen when the OVN DB is very large. This work is also tracked under Bugzilla: https://bugzilla.redhat.com/1955271 ** 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/1926653 Title: [ovn] ml2/ovn may time out connecting to ovsdb server and stays dead in the water Status in neutron: New Bug description: Right now, the IDL connections between ml2/ovn are not resilient enough when connecting. It doesn't make sense to give up on that since the ml2/ovn is useless w/out that access. If ovsdb-server is slow and takes more than timeout seconds, everything reconnecting after partial downloads and starting over is not going to make things better. That is particularly likely to happen when the OVN DB is very large. This work is also tracked under Bugzilla: https://bugzilla.redhat.com/1955271 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1926653/+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 1921491] [NEW] ml2/ovn should not be calling neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api
Public bug reported: While using a ml2/ovn deployment, there is no need for using RPC based DHCP, since that is handled via ovn-controller. Still, we currently enable DhcpAgentNotifyAPI unconditionally [0], which seems wrong. One side effect of that is that we periodically see the following warning log. Good news is that this does not seem to be breaking anything. 2021-03-25 20:23:59.155 28 WARNING neutron.scheduler.dhcp_agent_scheduler [req-d28046f6-897a-4644-a64e- 8338b81d0676 72126141799d44f6a82b803bde3ed144 b3d574eefb1b4eba88ba2b93a2b3cd21 - default default] No more DHCP agents 2021-03-25 20:23:59.158 28 WARNING neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [req- d28046f6-897a-4644-a64e-8338b81d0676 72126141799d44f6a82b803bde3ed144 b3d574eefb1b4eba88ba2b93a2b3cd21 - default default] Unable to schedule network c578ba7a-156a-4ec5-b7c9-37aeba1331d3: no agents available; will retry on subsequent port and subnet creation events. According to Rodolfo, we must be careful in adding a conditional to that code, so it does not adversely affect nova. He also points out that there is a flag that may be what we can use for this. """ so, IMO, we should make this conditional (or maybe that's more complicated, we need to know that no compute is running a DHCP agent) but be careful: we cannot disable this if we don't know any compute is not using dhcp agents there is a flag (in master) cfg.CONF.enable_traditional_dhcp used to enable/disable this RPC related to the DHCP server on OVS (a new feature not merged yet) we can implement something similar """ [0]: https://github.com/openstack/neutron/blob/de3681ed3b0d0a54f0b8b59628fa50f25d5e737e/neutron/plugins/ml2/plugin.py#L325-L327 ** Affects: neutron Importance: Medium 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/1921491 Title: ml2/ovn should not be calling neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api Status in neutron: New Bug description: While using a ml2/ovn deployment, there is no need for using RPC based DHCP, since that is handled via ovn-controller. Still, we currently enable DhcpAgentNotifyAPI unconditionally [0], which seems wrong. One side effect of that is that we periodically see the following warning log. Good news is that this does not seem to be breaking anything. 2021-03-25 20:23:59.155 28 WARNING neutron.scheduler.dhcp_agent_scheduler [req-d28046f6-897a-4644-a64e- 8338b81d0676 72126141799d44f6a82b803bde3ed144 b3d574eefb1b4eba88ba2b93a2b3cd21 - default default] No more DHCP agents 2021-03-25 20:23:59.158 28 WARNING neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [req- d28046f6-897a-4644-a64e-8338b81d0676 72126141799d44f6a82b803bde3ed144 b3d574eefb1b4eba88ba2b93a2b3cd21 - default default] Unable to schedule network c578ba7a-156a-4ec5-b7c9-37aeba1331d3: no agents available; will retry on subsequent port and subnet creation events. According to Rodolfo, we must be careful in adding a conditional to that code, so it does not adversely affect nova. He also points out that there is a flag that may be what we can use for this. """ so, IMO, we should make this conditional (or maybe that's more complicated, we need to know that no compute is running a DHCP agent) but be careful: we cannot disable this if we don't know any compute is not using dhcp agents there is a flag (in master) cfg.CONF.enable_traditional_dhcp used to enable/disable this RPC related to the DHCP server on OVS (a new feature not merged yet) we can implement something similar """ [0]: https://github.com/openstack/neutron/blob/de3681ed3b0d0a54f0b8b59628fa50f25d5e737e/neutron/plugins/ml2/plugin.py#L325-L327 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1921491/+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 1914757] [NEW] [ovn] add ovn driver for security-group-logging
Public bug reported: The request is about to have a log file where security groups events are logged to be consumed by security department, like any other commercial firewall vendor has. This is a follow up to: https://bugs.launchpad.net/neutron/+bug/1468366 ml2/OVN has a functionality gap related to the support for security-group-logging: https://blueprints.launchpad.net/neutron/+spec/security-group-logging This work is also tracked under Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1619266 ** Affects: neutron Importance: Undecided Assignee: Flavio Fernandes (ffernand) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1914757 Title: [ovn] add ovn driver for security-group-logging Status in neutron: In Progress Bug description: The request is about to have a log file where security groups events are logged to be consumed by security department, like any other commercial firewall vendor has. This is a follow up to: https://bugs.launchpad.net/neutron/+bug/1468366 ml2/OVN has a functionality gap related to the support for security-group-logging: https://blueprints.launchpad.net/neutron/+spec/security-group-logging This work is also tracked under Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1619266 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1914757/+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 1909038] [NEW] TypeError: lrp_set_options() takes 2 positional arguments but 3 were given
Public bug reported: I see the following error when restarting the neutron process on master devstack deployment: TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics [None req-be925f41-7b5f-4e04-893a-282cdbb5d137 None None] Failed to call immediate 'neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance.DBInconsistenciesPeriodics.check_for_fragmentation_support' (it runs every 600.00 seconds): TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics Traceback (most recent call last): Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 293, in run Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics work() Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 67, in __call__ Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics return self.callback(*self.args, **self.kwargs) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 181, in decorator Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics return f(*args, **kwargs) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py", line 548, in check_for_fragmentation_support Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics self._ovn_client.set_gateway_mtu(context, net) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py", line 1624, in set_gateway_mtu Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics commands.append(self._nb_idl.lrp_set_options(lrp_name, options)) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics ** 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/1909038 Title: TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Status in neutron: New Bug description: I see the following error when restarting the neutron process on master devstack deployment: TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics [None req-be925f41-7b5f-4e04-893a-282cdbb5d137 None None] Failed to call immediate 'neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance.DBInconsistenciesPeriodics.check_for_fragmentation_support' (it runs every 600.00 seconds): TypeError: lrp_set_options() takes 2 positional arguments but 3 were given Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics Traceback (most recent call last): Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 293, in run Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics work() Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 67, in __call__ Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics return self.callback(*self.args, **self.kwargs) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/usr/local/lib/python3.8/dist-packages/futurist/periodics.py", line 181, in decorator Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics return f(*args, **kwargs) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py", line 548, in check_for_fragmentation_support Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics self._ovn_client.set_gateway_mtu(context, net) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics File "/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py", line 1624, in set_gateway_mtu Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics commands.append(self._nb_idl.lrp_set_options(lrp_name, options)) Dec 22 21:02:06 stack neutron-server[200078]: ERROR futurist.periodics TypeError:
[Yahoo-eng-team] [Bug 1891517] [NEW] neutron.tests.unit.common.test_utils.TimerTestCase.test__enter_with_timeout fails once in a while
Public bug reported: While running job openstack-tox-lower-constraints https://zuul.opendev.org/t/openstack/job/openstack-tox-lower-constraints I see intermittent failures that look lie this: neutron.tests.unit.common.test_utils.TimerTestCase.test__enter_with_timeout --- Captured traceback: ~~~ b'Traceback (most recent call last):' b' File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 182, in func' b'return f(self, *args, **kwargs)' b' File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/unit/common/test_utils.py", line 551, in test__enter_with_timeout' b'self.assertEqual(1, round(timer.total_seconds()))' b' File "/home/zuul/src/opendev.org/openstack/neutron/.tox/lower-constraints/lib/python3.6/site-packages/testtools/testcase.py", line 411, in assertEqual' b'self.assertThat(observed, matcher, message)' b' File "/home/zuul/src/opendev.org/openstack/neutron/.tox/lower-constraints/lib/python3.6/site-packages/testtools/testcase.py", line 498, in assertThat' b'raise mismatch_error' b'testtools.matchers._impl.MismatchError: 1 != 2' b'' The code needs to do better in the rounding of the second. ;) Reference run failure: https://zuul.opendev.org/t/openstack/build/f031ac5c396a4610853fba5178e9fd1b ** 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/1891517 Title: neutron.tests.unit.common.test_utils.TimerTestCase.test__enter_with_timeout fails once in a while Status in neutron: New Bug description: While running job openstack-tox-lower-constraints https://zuul.opendev.org/t/openstack/job/openstack-tox-lower- constraints I see intermittent failures that look lie this: neutron.tests.unit.common.test_utils.TimerTestCase.test__enter_with_timeout --- Captured traceback: ~~~ b'Traceback (most recent call last):' b' File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/base.py", line 182, in func' b'return f(self, *args, **kwargs)' b' File "/home/zuul/src/opendev.org/openstack/neutron/neutron/tests/unit/common/test_utils.py", line 551, in test__enter_with_timeout' b'self.assertEqual(1, round(timer.total_seconds()))' b' File "/home/zuul/src/opendev.org/openstack/neutron/.tox/lower-constraints/lib/python3.6/site-packages/testtools/testcase.py", line 411, in assertEqual' b'self.assertThat(observed, matcher, message)' b' File "/home/zuul/src/opendev.org/openstack/neutron/.tox/lower-constraints/lib/python3.6/site-packages/testtools/testcase.py", line 498, in assertThat' b'raise mismatch_error' b'testtools.matchers._impl.MismatchError: 1 != 2' b'' The code needs to do better in the rounding of the second. ;) Reference run failure: https://zuul.opendev.org/t/openstack/build/f031ac5c396a4610853fba5178e9fd1b To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1891517/+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 1891243] [NEW] neutron tempest failure: neutron_tempest_plugin.api.test_extensions.ExtensionsTest.test_list_extensions_includes_all
Public bug reported:
testtools.matchers._impl.MismatchError: 'segment' not in {'...'}
cd /opt/stack/tempest
$ tox -e all-plugin -- test_extensions
all-plugin develop-inst-noop: /opt/stack/tempest
all-plugin installed:
alembic==1.4.2,amqp==2.6.1,aniso8601==8.0.0,apparmor==2.12,appdirs==1.4.4,asn1crypto==0.24.0,attrs==19.3.0,Automat==0.6.0,automaton==2.2.0,Babel==2.8.0,bcrypt==3.1.7,beautifulsoup4==4.9.1,blinker==1.4,cachetools==4.1.1,castellan==3.4.0,certifi==2020.6.20,cffi==1.14.1,chardet==3.0.4,click==7.1.2,cliff==3.4.0,cloud-init==20.2,cmd2==1.3.1,colorama==0.4.3,command-not-found==0.3,configobj==5.0.6,constantly==15.1.0,cryptography==3.0,cursive==0.2.2,dataclasses==0.7,ddt==1.4.1,debtcollector==2.2.0,decorator==4.4.2,defusedxml==0.6.0,distlib==0.3.1,distro-info===0.18ubuntu0.18.04.1,Django==2.2.15,django-appconf==1.0.4,django-compressor==2.4,django-debreach==2.0.1,django-pyscss==2.0.2,dnspython==1.16.0,dogpile.cache==1.0.2,enmerkar==0.7.1,etcd3==0.12.0,etcd3gw==0.2.6,eventlet==0.26.1,extras==1.0.0,fancycompleter==0.9.1,fasteners==0.14.1,filelock==3.0.12,fixtures==3.0.0,Flask==1.1.2,Flask-RESTful==0.3.8,future==0.18.2,futurist==2.2.0,-e
git+https://opendev.org/openstack/glance.git@ed3296b23a452391bbe6e060d4b49235523e#egg=glance,glance-store==2.1.0,greenlet==0.4.16,grpcio==1.31.0,-e
git+https://opendev.org/openstack/horizon.git@a2a173d2c5fa9173793ae3deed194dde7c9a802f#egg=horizon,httplib2==0.18.1,hyperlink==17.3.1,idna==2.10,importlib-metadata==1.7.0,importlib-resources==3.0.0,incremental==16.10.1,ipython==5.5.0,ipython-genutils==0.2.0,iso8601==0.1.12,itsdangerous==1.1.0,Jinja2==2.11.2,jmespath==0.10.0,jsonpatch==1.26,jsonpointer==2.0,jsonschema==3.2.0,keyring==10.6.0,keyrings.alt==3.0,-e
git+https://opendev.org/openstack/keystone.git@952959fb872b25d4ad525056012e1667efb4eb60#egg=keystone,keystoneauth1==4.2.1,keystonemiddleware==9.1.0,kombu==5.0.0,language-selector==0.1,LibAppArmor==2.12,libvirt-python==6.6.0,linecache2==1.0.0,logutils==0.3.5,lxml==4.5.2,Mako==1.1.3,MarkupSafe==1.1.1,microversion-parse==1.0.1,monotonic==1.5,msgpack==1.0.0,munch==2.5.0,mysqlclient==1.3.10,netaddr==0.8.0,netifaces==0.10.9,networkx==2.4,-e
git+https://opendev.org/openstack/neutron.git@75afd4142d99c5f3601647c9e72c4d7d2027b65b#egg=neutron,neutron-lib==2.5.0,-e
git+https://opendev.org/openstack/neutron-tempest-plugin.git@dee81bc0fafe1b834cb4f92cf30621b361d386e1#egg=neutron_tempest_plugin,nose==1.3.7,-e
git+https://opendev.org/openstack/nova.git@64980bd78cba04e011ea78ed229b60e95204d60f#egg=nova,numpy==1.19.1,oauthlib==3.1.0,-e
git+https://opendev.org/openstack/placement.git@4b95c078cc75987979a96bceafce152d6153adcf#egg=openstack_placement,openstacksdk==0.48.0,os-brick==3.2.0,os-client-config==2.1.0,os-ken==1.1.0,os-resource-classes==1.0.0,os-service-types==1.7.0,os-testr==2.0.0,os-traits==2.4.0,os-vif==2.1.0,os-win==5.1.0,os-xenapi==0.3.4,osc-lib==2.2.0,osc-placement==2.0.0,oslo.cache==2.5.0,oslo.concurrency==4.2.0,oslo.config==8.3.1,oslo.context==3.1.0,oslo.db==8.3.0,oslo.i18n==5.0.0,oslo.log==4.3.0,oslo.messaging==12.2.2,oslo.middleware==4.1.0,oslo.policy==3.3.2,oslo.privsep==2.3.0,oslo.reports==2.1.0,oslo.rootwrap==6.1.0,oslo.serialization==4.0.0,oslo.service==2.3.2,oslo.upgradecheck==1.1.0,oslo.utils==4.4.0,oslo.versionedobjects==2.2.0,osprofiler==3.3.0,ovs==2.13.0,-e
[Yahoo-eng-team] [Bug 1888736] [NEW] [OVN]: creating a local switch port that has no tags should not fail
Public bug reported:
When creating a network, I see the following error (full log attached):
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
neutron.api.rpc.handlers.resources_rpc [None req-6ac75e1f-c23b-46c4
-9b5a-14e14c235959 admin admin] Pushing event updated for resources:
{'Network': ['ID=0ab805f8-a386-413c-be2a-
88240cf5d4af,revision_number=1']} {{(pid=27516) push
/opt/stack/neutron/neutron/api/rpc/handlers/resources_rpc.py:243}}
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1 command(idx=0):
LsAddCommand(switch=neutron-0ab805f8-a386-413c-be2a-88240cf5d4af,
columns={'external_ids': {'neutron:network_name': 'public', 'neutron:mtu':
'1500', 'neutron:revision_number': '1'}, 'other_config': {'mcast_snoop':
'false', 'mcast_flood_unregistere\
d': 'false'}}, may_exist=True) {{(pid=27516) do_commit
/usr/local/lib/python3.6/dist-packages/ovsdbapp/backend/ovs_idl/transaction.py:87}}
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1 command(idx=1):
AddLSwitchPortCommand(lport=provnet-4ad8f85e-
e7af-4437-8556-73892bff4076, lswitch=neutron-0ab805f8-a386-413c-be2a-
88240cf5d4af, may_exist=True, columns={'addresses': ['unknown'],
'external_ids': {}, 'type': 'localnet', 'tag': None, 'options':
{'network_name': 'public'}}) {{(pid=27516) do_commit
/usr/local/lib/python3.6/dist-
packages/ovsdbapp/backend/ovs_idl/transaction.py:87}}
Jul 23 20:52:06 stack neutron-server[27492]: ERROR
ovsdbapp.backend.ovs_idl.vlog [-] attempting to write bad value to
column tag (ovsdb error: expected integer, got ):
ovs.db.error.Error: ovsdb error: expected integer, got
Steps to reproduce:
Create a public network in openstack cluster?!?
** 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/1888736
Title:
[OVN]: creating a local switch port that has no tags should not fail
Status in neutron:
New
Bug description:
When creating a network, I see the following error (full log
attached):
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
neutron.api.rpc.handlers.resources_rpc [None req-6ac75e1f-c23b-46c4
-9b5a-14e14c235959 admin admin] Pushing event updated for resources:
{'Network': ['ID=0ab805f8-a386-413c-be2a-
88240cf5d4af,revision_number=1']} {{(pid=27516) push
/opt/stack/neutron/neutron/api/rpc/handlers/resources_rpc.py:243}}
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1 command(idx=0):
LsAddCommand(switch=neutron-0ab805f8-a386-413c-be2a-88240cf5d4af,
columns={'external_ids': {'neutron:network_name': 'public', 'neutron:mtu':
'1500', 'neutron:revision_number': '1'}, 'other_config': {'mcast_snoop':
'false', 'mcast_flood_unregistere\
d': 'false'}}, may_exist=True) {{(pid=27516) do_commit
/usr/local/lib/python3.6/dist-packages/ovsdbapp/backend/ovs_idl/transaction.py:87}}
Jul 23 20:52:06 stack neutron-server[27492]: DEBUG
ovsdbapp.backend.ovs_idl.transaction [-] Running txn n=1
command(idx=1): AddLSwitchPortCommand(lport=provnet-4ad8f85e-
e7af-4437-8556-73892bff4076, lswitch=neutron-0ab805f8-a386-413c-be2a-
88240cf5d4af, may_exist=True, columns={'addresses': ['unknown'],
'external_ids': {}, 'type': 'localnet', 'tag': None, 'options':
{'network_name': 'public'}}) {{(pid=27516) do_commit
/usr/local/lib/python3.6/dist-
packages/ovsdbapp/backend/ovs_idl/transaction.py:87}}
Jul 23 20:52:06 stack neutron-server[27492]: ERROR
ovsdbapp.backend.ovs_idl.vlog [-] attempting to write bad value to
column tag (ovsdb error: expected integer, got ):
ovs.db.error.Error: ovsdb error: expected integer, got
Steps to reproduce:
Create a public network in openstack cluster?!?
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1888736/+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 1885114] [NEW] job neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri may not be using ussuri
Public bug reported: While looking at neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri job's local conf, I noticed that the neutron plugin is not referencing stable/ussuri, as implied by the name. Example: https://review.opendev.org/#/c/732553/4 zuul jobs: neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri https://zuul.opendev.org/t/openstack/build/d512052fd71340638c2a6752077f8918 Logs --> Controller --> logs --> local_conf.txt Line 80 ==> enable_plugin neutron https://opendev.org/openstack/neutron.git It should be: enable_plugin neutron https://opendev.org/openstack/neutron.git stable/ussuri https://zuul.opendev.org/t/openstack/build/d512052fd71340638c2a6752077f8918/log/controller/logs/local_conf.txt#80 ** 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/1885114 Title: job neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri may not be using ussuri Status in neutron: New Bug description: While looking at neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri job's local conf, I noticed that the neutron plugin is not referencing stable/ussuri, as implied by the name. Example: https://review.opendev.org/#/c/732553/4 zuul jobs: neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri https://zuul.opendev.org/t/openstack/build/d512052fd71340638c2a6752077f8918 Logs --> Controller --> logs --> local_conf.txt Line 80 ==> enable_plugin neutron https://opendev.org/openstack/neutron.git It should be: enable_plugin neutron https://opendev.org/openstack/neutron.git stable/ussuri https://zuul.opendev.org/t/openstack/build/d512052fd71340638c2a6752077f8918/log/controller/logs/local_conf.txt#80 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1885114/+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 1879407] [NEW] [OVN] Modifying FIP that is no associated causes ovn_revision_numbers to go stale
Public bug reported:
NOTE: This is a low priority issue, mostly because it eventually gets
fixed by maintenance task
CheckRevisionNumberCommand relies in finding a corresponding entry in OVN's NAT
table
in order to update the OVN_REV_NUM_EXT_ID_KEY to keep ovn and neutron databases
in sync.
Ref: http://lucasgom.es/posts/neutron_ovn_database_consistency.html
Trouble is that unless the floating ip is associated, there will be no
entries in OVN's NAT table, causing the call to
db_rev.bump_revision(context, floatingip, ovn_const.TYPE_FLOATINGIPS)
to not take place.
Steps to reproduce it:
# create a floating ip but do not associate it with anything so router_id is
None
FIP=172.24.4.8
openstack floating ip create --floating-ip-address ${FIP} public
FIP_UUID=$(openstack floating ip show ${FIP} -f value -c id) ; echo $FIP_UUID
# Mess with its name, which will bump revision on fip object
openstack floating ip set --description foo ${FIP_UUID}
Code when there is no NAT for a given FIP makes line 1044 skip line 1045
https://github.com/openstack/neutron/blob/15088b39bab715e40d8161a85c95ca400708c83f/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#L1044
check_rev_cmd.result is None
The dbs are now the inconsistent state
mysql> use neutron;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select * from standardattributes where resource_type="floatingips";
++---+-+-+-+-+
| id | resource_type | created_at | updated_at | description
| revision_number |
++---+-+-+-+-+
| 49 | floatingips | 2020-05-18 20:56:51 | 2020-05-18 20:58:58 | foo2
| 2 |
++---+-+-+-+-+
1 row in set (0.01 sec)
mysql> select * from ovn_revision_numbers where resource_type="floatingips";
+--+--+---+-+-+-+
| standard_attr_id | resource_uuid| resource_type |
revision_number | created_at | updated_at |
+--+--+---+-+-+-+
| 49 | 5a1e1ffa-0312-4e78-b7a0-551c396bcf6b | floatingips |
0 | 2020-05-18 20:56:51 | 2020-05-18 20:57:08 |
+--+--+---+-+-+-+
1 row in set (0.00 sec)
Maintenance task fixes it up later
May 18 21:50:29 stack neutron-server[909]: DEBUG futurist.periodics [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Submitting periodic
callback 'neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance.DBIn\
consistenciesPeriodics.check_for_inconsistencies' {{(pid=3186)
_process_scheduled
/usr/local/lib/python3.6/dist-packages/futurist/periodics.py:642}}
May 18 21:50:29 stack neutron-server[909]: DEBUG
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Maintenance task:
Synchronizing Neutron and OVN datab\
ases {{(pid=3186) check_for_inconsistencies
/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py:347}}
May 18 21:50:29 stack neutron-server[909]: DEBUG
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Maintenance task: Number of
inconsistencies found at \
create/update: floatingips=1 {{(pid=3186) _log
/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py:325}}
May 18 21:50:29 stack neutron-server[909]: DEBUG
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Maintenance task: Fixing
resource 6b876a35-d286-4407-\
b538-9ce07ab1a281 (type: floatingips) at create/update {{(pid=3186)
check_for_inconsistencies
/opt/stack/neutron/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py:359}}
May 18 21:50:29 stack neutron-server[909]: INFO
neutron.db.ovn_revision_numbers_db [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Successfully bumped
revision number for resource 6b876a35-d286-4407-b538-9ce07ab1\
a281 (type: floatingips) to 1
May 18 21:50:29 stack neutron-server[909]: INFO
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance [None
req-35091ee8-f2fe-47cc-b757-8bb70f750b47 None None] Maintenance task:
Synchronization finished (took 0.08 \
seconds)
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
NOTE: This is a low priority issue,
[Yahoo-eng-team] [Bug 1878299] [NEW] [floatingip port_forwarding] changing external port to used value hangs with retriable exception
Public bug reported:
When trying to change external-protocol-port to a value that is already used by
another pf row, there is no error checking and we end up 'stuck' until the api
times out. The neutron db is catching
the improper config, but the validation should likely not allow it to get that
far.
(overcloud) [stack@undercloud-0 ~]$ openstack floating ip port forwarding list
${FIP_UUID}
+--+--+-+---+---+--+
| ID | Internal Port ID |
Internal IP Address | Internal Port | External Port | Protocol |
+--+--+-+---+---+--+
| 5a8515b8-9e03-442f-a8d7-41acd11f59b5 | 63767606-35ea-4c08-b6c8-1216d0c407e8 |
192.168.30.159 |22 | 2021 | tcp |
| 60693ea5-e985-404d-87ce-798dd4f6f4da | d5a31eba-89cb-40a8-ba98-d6ca1a8fffb1 |
192.168.30.84 |22 | 2020 | tcp |
+--+--+-+---+---+--+
(overcloud) [stack@undercloud-0 ~]$
(overcloud) [stack@undercloud-0 ~]$
# now, doing something invalid: try to change external-protocol-port of $PF_ID2
to the port that is being used by $PF_ID (60693ea5-e985-404d-87ce-798dd4f6f4da)
(overcloud) [stack@undercloud-0 ~]$ echo ${PF_ID2}
5a8515b8-9e03-442f-a8d7-41acd11f59b5
(overcloud) [stack@undercloud-0 ~]$ time openstack floating ip port
forwarding set --external-protocol-port 2020 ${FIP_UUID} ${PF_ID2}
HttpException: 504: Server Error for url:
http://10.0.0.125:9696/v2.0/floatingips/aee2c979-31a1-453a-b508-319c71fee9dc/port_forwardings/5a8515b8-9e03
-442f-a8d7-41acd11f59b5, The server didn't respond in time.: 504 Gateway
Time-out
real2m3.552s
user0m1.672s
sys 0m0.727s
=-==-
[root@controller-0 neutron]# tail -F server.log
...
2020-05-12 17:54:15.900 26 DEBUG neutron.api.v2.base
[req-f0726861-9f58-4e35-b3b0-15a8bd4ada5b 251059acfcae468c89fa33c988910832
ea7d486cda284d8fa7f3eaf8351f080d - default default] Request body:
{'port_forwarding': {'external_port': 2020}} prepare_request_body
/usr/lib/python3.6/site-packages/neutron/api/v2/base.py:719
2020-05-12 17:54:16.137 28 DEBUG neutron.wsgi [-] (28) accepted ('172.17.1.38',
57154) server /usr/lib/python3.6/site-packages/eventlet/wsgi.py:985
2020-05-12 17:54:16.370 26 DEBUG neutron_lib.db.api
[req-f0726861-9f58-4e35-b3b0-15a8bd4ada5b 251059acfcae468c89fa33c988910832
ea7d486cda284d8fa7f3eaf8351f080d - default default] Retry wrapper got retriable
exception: (pymysql.err.IntegrityError) (1062, "Duplicate entry
'aee2c979-31a1-453a-b508-319c71fee9dc-2020-tcp' for key
'uniq_port_forwardings0floatingip_id0external_port0protocol'")
[SQL: UPDATE portforwardings SET external_port=%(external_port)s WHERE
portforwardings.id = %(portforwardings_id)s]
[parameters: {'external_port': 2020, 'portforwardings_id':
'5a8515b8-9e03-442f-a8d7-41acd11f59b5'}]
(Background on this error at: http://sqlalche.me/e/gkpj) wrapped
/usr/lib/python3.6/site-packages/neutron_lib/db/api.py:183
2020-05-12 17:54:16.371 26 DEBUG oslo_db.api
[req-f0726861-9f58-4e35-b3b0-15a8bd4ada5b 251059acfcae468c89fa33c988910832
ea7d486cda284d8fa7f3eaf8351f080d - default default] Performing DB retry for
function neutron.api.v2.base.Controller._update wrapper
/usr/lib/python3.6/site-packages/oslo_db/api.py:156
2020-05-12 17:54:16.458 28 DEBUG neutron.wsgi [-] (28) accepted
('172.17.1.141', 48380) server
/usr/lib/python3.6/site-packages/eventlet/wsgi.py:985
2020-05-12 17:54:17.882 28 DEBUG neutron.wsgi [-] (28) accepted ('172.17.1.84',
39608) server /usr/lib/python3.6/site-packages/eventlet/wsgi.py:985
2020-05-12 17:54:17.946 26 DEBUG neutron.api.v2.base
[req-f0726861-9f58-4e35-b3b0-15a8bd4ada5b 251059acfcae468c89fa33c988910832
ea7d486cda284d8fa7f3eaf8351f080d - default default] Request body:
{'port_forwarding': {'external_port': 2020}} prepare_request_body
/usr/lib/python3.6/site-packages/neutron/api/v2/base.py:719
2020-05-12 17:54:18.145 29 DEBUG neutron.wsgi [-] (29) accepted ('172.17.1.38',
57244) server /usr/lib/python3.6/site-packages/eventlet/wsgi.py:985
2020-05-12 17:54:18.292 26 DEBUG neutron_lib.db.api
[req-f0726861-9f58-4e35-b3b0-15a8bd4ada5b 251059acfcae468c89fa33c988910832
ea7d486cda284d8fa7f3eaf8351f080d - default default] Retry wrapper got retriable
exception: (pymysql.err.IntegrityError) (1062, "Duplicate entry
'aee2c979-31a1-453a-b508-319c71fee9dc-2020-tcp' for key
'uniq_port_forwardings0floatingip_id0external_port0protocol'")
[SQL: UPDATE portforwardings SET external_port=%(external_port)s WHERE
portforwardings.id = %(portforwardings_id)s]
[parameters: {'external_port': 2020, 'portforwardings_id':
'5a8515b8-9e03-442f-a8d7-41acd11f59b5'}]
(Background on
[Yahoo-eng-team] [Bug 1877447] [NEW] [RFE] Add TCP/UDP port forwarding extension to OVN
Public bug reported: Floating IP Port Forwarding needs to be implemented to ml2/OVN This is a functionality gap that currently exists between ml2/ovs and ml2/ovn, mentioned in [1]. Blueprint information is available here [2]. [1]: https://review.opendev.org/#/c/658414/19/specs/ussuri/ml2ovs-ovn-convergence.rst [2]: https://blueprints.launchpad.net/neutron/+spec/port-forwarding ** Affects: neutron Importance: Undecided Assignee: Flavio Fernandes (ffernand) Status: In Progress ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) ** Description changed: + Floating IP Port Forwarding needs to be implemented to ml2/OVN - Floating IP Port Forwarding is needs to be implemented to ml2/OVN - - This is a functionality gap that currently exists between ml2/ovs and ml2/ovn, - mentioned in [1]. + This is a functionality gap that currently exists between ml2/ovs and + ml2/ovn, mentioned in [1]. Blueprint information is available here [2]. [1]: https://review.opendev.org/#/c/658414/19/specs/ussuri/ml2ovs-ovn-convergence.rst [2]: https://blueprints.launchpad.net/neutron/+spec/port-forwarding -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1877447 Title: [RFE] Add TCP/UDP port forwarding extension to OVN Status in neutron: In Progress Bug description: Floating IP Port Forwarding needs to be implemented to ml2/OVN This is a functionality gap that currently exists between ml2/ovs and ml2/ovn, mentioned in [1]. Blueprint information is available here [2]. [1]: https://review.opendev.org/#/c/658414/19/specs/ussuri/ml2ovs-ovn-convergence.rst [2]: https://blueprints.launchpad.net/neutron/+spec/port-forwarding To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1877447/+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 1877195] [NEW] [ovn] neutron devstack needs to support openflow15
Public bug reported: OVN has been changed to use OF15 see [1] Because of that, devstack configuration scripts must be updated to stop using the hard coded Openflow13 protocol. Still, we should make this backwards compatible so it remains working on potentially older versions of OVN. The error you observe in this situation looks like this: tail -F /opt/stack/logs/ovs-vswitchd.log 2020-05-06T21:04:31.488Z|00482|vconn|WARN|unix#341: version negotiation failed (we support version 0x04, peer support s version 0x06) To work around this issue on devstack, set the protocol and restart vswitchd service: systemctl restart devstack@ovs-vswitchd.service https://github.com/ovn- org/ovn/commit/6ec0b82038052866533f12823fe410308b3e457a ** Affects: neutron Importance: Undecided Assignee: Flavio Fernandes (ffernand) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1877195 Title: [ovn] neutron devstack needs to support openflow15 Status in neutron: In Progress Bug description: OVN has been changed to use OF15 see [1] Because of that, devstack configuration scripts must be updated to stop using the hard coded Openflow13 protocol. Still, we should make this backwards compatible so it remains working on potentially older versions of OVN. The error you observe in this situation looks like this: tail -F /opt/stack/logs/ovs-vswitchd.log 2020-05-06T21:04:31.488Z|00482|vconn|WARN|unix#341: version negotiation failed (we support version 0x04, peer support s version 0x06) To work around this issue on devstack, set the protocol and restart vswitchd service: systemctl restart devstack@ovs-vswitchd.service https://github.com/ovn- org/ovn/commit/6ec0b82038052866533f12823fe410308b3e457a To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1877195/+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 1876148] [NEW] OVNL3RouterPlugin should use class RouterPluginBase
Public bug reported:
The class OVNL3RouterPlugin in neutron/services/ovn_l3/plugin.py
implements RouterPluginBase but yet is not declaring it such via Inheritance.
This issue was found when trying to invoke
add_router_interface(self, context, router_id, interface_info=None)
from neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py
def _create_lrouter_port(self, context, port):
router_id = port['device_id']
self._ovn_client._l3_plugin.add_router_interface(
context, router_id, {'port_id': port['id']}, may_exist=True)
where the param may_exist does not exist. That caused the failure below.
By complying with RouterPluginBase's abstract methods, issues like this
would have been discovered sooner.
```
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance File
"/opt/stack/neutron/neutron/plugins/ml2/driver\
s/ovn/mech_driver/ovsdb/maintenance.py", line 401, in _create_lrouter_port
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance context,
router_id, {'port_id': port['id']}, may_\
exist=True)
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance TypeError:
add_router_interface() got an unexpected k\
eyword argument 'may_exist'
```
** Affects: neutron
Importance: Undecided
Assignee: Flavio Fernandes (ffernand)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Flavio Fernandes (ffernand)
** Summary changed:
- OVNL3RouterPlugin should use class L3(extensions.APIExtensionDescriptor)
+ OVNL3RouterPlugin should use class RouterPluginBase
** Description changed:
-
The class OVNL3RouterPlugin in neutron/services/ovn_l3/plugin.py
- implements L3 but yet is not declaring it such via Inheritance.
+ implements RouterPluginBase but yet is not declaring it such via Inheritance.
This issue was found when trying to invoke
- add_router_interface(self, context, router_id, interface_info=None)
+ add_router_interface(self, context, router_id, interface_info=None)
from neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py
- def _create_lrouter_port(self, context, port):
- router_id = port['device_id']
- self._ovn_client._l3_plugin.add_router_interface(
- context, router_id, {'port_id': port['id']}, may_exist=True)
+ def _create_lrouter_port(self, context, port):
+ router_id = port['device_id']
+ self._ovn_client._l3_plugin.add_router_interface(
+ context, router_id, {'port_id': port['id']}, may_exist=True)
where the param may_exist does not exist. That caused the failure below.
- By complying with L3's abstract methods, issues like this would have been
- discovered sooner.
-
+ By complying with RouterPluginBase's abstract methods, issues like this
+ would have been discovered sooner.
```
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance File
"/opt/stack/neutron/neutron/plugins/ml2/driver\
s/ovn/mech_driver/ovsdb/maintenance.py", line 401, in _create_lrouter_port
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance context,
router_id, {'port_id': port['id']}, may_\
exist=True)
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance TypeError:
add_router_interface() got an unexpected k\
eyword argument 'may_exist'
```
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1876148
Title:
OVNL3RouterPlugin should use class RouterPluginBase
Status in neutron:
New
Bug description:
The class OVNL3RouterPlugin in neutron/services/ovn_l3/plugin.py
implements RouterPluginBase but yet is not declaring it such via Inheritance.
This issue was found when trying to invoke
add_router_interface(self, context, router_id,
interface_info=None)
from neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/maintenance.py
def _create_lrouter_port(self, context, port):
router_id = port['device_id']
self._ovn_client._l3_plugin.add_router_interface(
context, router_id, {'port_id': port['id']}, may_exist=True)
where the param may_exist does not exist. That caused the failure
below.
By complying with RouterPluginBase's abstract methods, issues like
this would have been discovered sooner.
```
Apr 30 08:52:00 dstackvm neutron-server[1508]: ERROR
neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance File
"/opt/stack/neutron/neutron/plugins/ml2/driver\
s/ovn/mech_driver/ovsdb/maintenance.py", line 401, in _create_lrouter_port
[Yahoo-eng-team] [Bug 1871427] [NEW] neutron ovn db clients need more logs if they fail to connect to db
Public bug reported: Currently, the ovn_driver and ovn_metadata are not good in indicating failure to connect to the ovn database. That makes it hard to know when it is working properly. refs: https://github.com/openstack/neutron/blob/75f6f624bcc0b88b2ae38c49298668ada8e093b1/neutron/agent/ovn/metadata/ovsdb.py#L50 https://github.com/openstack/ovn-octavia- provider/blob/bbb1755176f50f636af413e88df3f1744a72b149/ovn_octavia_provider/driver.py#L180 ** Affects: neutron Importance: Undecided Assignee: Flavio Fernandes (ffernand) Status: New ** Changed in: neutron Assignee: (unassigned) => Flavio Fernandes (ffernand) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1871427 Title: neutron ovn db clients need more logs if they fail to connect to db Status in neutron: New Bug description: Currently, the ovn_driver and ovn_metadata are not good in indicating failure to connect to the ovn database. That makes it hard to know when it is working properly. refs: https://github.com/openstack/neutron/blob/75f6f624bcc0b88b2ae38c49298668ada8e093b1/neutron/agent/ovn/metadata/ovsdb.py#L50 https://github.com/openstack/ovn-octavia- provider/blob/bbb1755176f50f636af413e88df3f1744a72b149/ovn_octavia_provider/driver.py#L180 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1871427/+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
