[Yahoo-eng-team] [Bug 1893618] Re: periodic-tripleo-ci-centos-8-standalone-full-tempest-api-compute-master tempest test_shelve_unshelve_server failing in component-pipeline
** 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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1893618
Title:
periodic-tripleo-ci-centos-8-standalone-full-tempest-api-compute-
master tempest test_shelve_unshelve_server failing in component-
pipeline
Status in OpenStack Compute (nova):
New
Status in tripleo:
Fix Released
Bug description:
https://logserver.rdoproject.org/openstack-component-
compute/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-
centos-8-standalone-full-tempest-api-compute-
master/b346467/logs/undercloud/var/log/tempest/stestr_results.html.gz
traceback-1: {{{
Traceback (most recent call last):
File
"/usr/lib/python3.6/site-packages/tempest/api/compute/servers/test_server_actions.py",
line 66, in tearDown
self.server_check_teardown()
File "/usr/lib/python3.6/site-packages/tempest/api/compute/base.py", line
220, in server_check_teardown
cls.server_id, 'ACTIVE')
File "/usr/lib/python3.6/site-packages/tempest/common/waiters.py", line 96,
in wait_for_server_status
raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (ServerActionsTestJSON:tearDown) Server
41f15309-34bb-430d-8dad-7b9c8362a851 failed to reach ACTIVE status and task
state "None" within the required time (300 s). Current status:
SHELVED_OFFLOADED. Current task state: None.
}}}
traceback-2: {{{
Traceback (most recent call last):
File
"/usr/lib/python3.6/site-packages/tempest/api/compute/servers/test_server_actions.py",
line 649, in _unshelve_server
server_info = self.client.show_server(self.server_id)['server']
File
"/usr/lib/python3.6/site-packages/tempest/lib/services/compute/servers_client.py",
line 145, in show_server
resp, body = self.get("servers/%s" % server_id)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 313, in get
return self.request('GET', url, extra_headers, headers)
File
"/usr/lib/python3.6/site-packages/tempest/lib/services/compute/base_compute_client.py",
line 48, in request
method, url, extra_headers, headers, body, chunked)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 702, in request
self._error_checker(resp, resp_body)
File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py",
line 808, in _error_checker
raise exceptions.NotFound(resp_body, resp=resp)
tempest.lib.exceptions.NotFound: Object not found
Details: {'code': 404, 'message': 'Instance None could not be found.'}
}}}
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/tempest/common/utils/__init__.py",
line 89, in wrapper
return f(*func_args, **func_kwargs)
File
"/usr/lib/python3.6/site-packages/tempest/api/compute/servers/test_server_actions.py",
line 666, in test_shelve_unshelve_server
waiters.wait_for_server_status(self.client, self.server_id, 'ACTIVE')
File "/usr/lib/python3.6/site-packages/tempest/common/waiters.py", line 96,
in wait_for_server_status
raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (ServerActionsTestJSON:test_shelve_unshelve_server) Server
41f15309-34bb-430d-8dad-7b9c8362a851 failed to reach ACTIVE status and task
state "None" within the required time (300 s). Current status:
SHELVED_OFFLOADED. Current task state: None.
Traceback in nova-compute logs https://logserver.rdoproject.org
/openstack-component-compute/opendev.org/openstack/tripleo-ci/master
/periodic-tripleo-ci-centos-8-standalone-full-tempest-api-compute-
master/b346467/logs/undercloud/var/log/containers/nova/nova-
compute.log.1.gz:-
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server
[req-9280bac1-da23-4f45-b01c-b6012198d97e 10fe2caa6924408485c181adfc7377e8
df52aad2e4da4f07b4b7b4ff6644e121 - default default] Exception during message
handling: AttributeError: 'NoneType' object has no attribute 'encode'
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server Traceback (most
recent call last):
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server File
"/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in
_process_incoming
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server res =
self.dispatcher.dispatch(message)
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server File
"/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 273,
in dispatch
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server return
self._do_dispatch(endpoint, method, ctxt, args)
2020-08-30 08:35:10.183 7 ERROR oslo_messaging.rpc.server File
"/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 193,
in _do_d
[Yahoo-eng-team] [Bug 1926149] [NEW] [OVN] Neutron server is filter by "subnet:segment_id", but not when OVS is used
Public bug reported:
When OVN backend is used, a manual HTTP request to retrieve the subnets
filtering by segment ID works fine: http://paste.openstack.org/
When OVS backend is used, this request returns:
{
"NeutronError": {
"type": "HTTPBadRequest",
"message": "['segment_id'] is invalid attribute for filtering",
"detail": ""
}
}
OVN does not have, in the ML2 supported list extensions, the extension
"filter-validation".
** Affects: neutron
Importance: Low
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: In Progress
** Changed in: neutron
Importance: Undecided => Low
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
** Description changed:
When OVN backend is used, a manual HTTP request to retrieve the subnets
- filtering by segment ID works fine:
-
- $ curl -s -H "X-Auth-Token: $OS_TOKEN" -H "Content-Type: application/json"
-X GET \
-
"https://overcloud.redhat.local:13696/v2.0/subnets?segment_id=2d0263b1-6e16-4f9f-94d1-e581c39e5d86";
+ filtering by segment ID works fine: http://paste.openstack.org/
When OVS backend is used, this request returns:
{
- "NeutronError": {
- "type": "HTTPBadRequest",
- "message": "['segment_id'] is invalid attribute for filtering",
- "detail": ""
- }
+ "NeutronError": {
+ "type": "HTTPBadRequest",
+ "message": "['segment_id'] is invalid attribute for filtering",
+ "detail": ""
+ }
}
-
- OVN does not have, in the ML2 supported list extensions, the extension
"filter-validation".
+ OVN does not have, in the ML2 supported list extensions, the extension
+ "filter-validation".
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1926149
Title:
[OVN] Neutron server is filter by "subnet:segment_id", but not when
OVS is used
Status in neutron:
In Progress
Bug description:
When OVN backend is used, a manual HTTP request to retrieve the
subnets filtering by segment ID works fine:
http://paste.openstack.org/
When OVS backend is used, this request returns:
{
"NeutronError": {
"type": "HTTPBadRequest",
"message": "['segment_id'] is invalid attribute for filtering",
"detail": ""
}
}
OVN does not have, in the ML2 supported list extensions, the extension
"filter-validation".
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1926149/+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 1925836] Re: [OVN] OVN metada should not need to monitor the enterily Chassis table
Reviewed: https://review.opendev.org/c/openstack/neutron/+/787780 Committed: https://opendev.org/openstack/neutron/commit/ce2c0010b93680bdcb6619940a84f8602769b837 Submitter: "Zuul (22348)" Branch:master commit ce2c0010b93680bdcb6619940a84f8602769b837 Author: Lucas Alvares Gomes Date: Fri Apr 23 17:32:07 2021 +0100 [OVN] MetadataProxyHandler to conditionally monitor both Chassis's tables If both Chassis and Chassis_Private tables are passed to the MetadataProxyHandler class we should conditionally monitor both of them. Change-Id: Iffd1deb977e92b9a600ab2603408ddf2eb387e18 Co-Authored-By: Terry Wilson Closes-Bug: #1925836 Signed-off-by: Lucas Alvares Gomes ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1925836 Title: [OVN] OVN metada should not need to monitor the enterily Chassis table Status in neutron: Fix Released Bug description: If both "Chassis" and "Chassis_Private" tables are passed to the MetadataProxyHandler class [0] the code will only limit the monitoring of the "Chassis_Private" table [1]. Ideally, both tables should be conditionally monitored instead. [0] https://github.com/openstack/neutron/blob/1ad9ca56b07ffdc9f7e0bc6a62af61961b9128eb/neutron/agent/ovn/metadata/agent.py#L240-L242 [1] https://github.com/openstack/neutron/blob/1ad9ca56b07ffdc9f7e0bc6a62af61961b9128eb/neutron/agent/ovn/metadata/ovsdb.py#L41-L44 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1925836/+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 1923423] Re: l3_router.service_providers DriverController's _attrs_to_driver is not py3 compatible
Reviewed: https://review.opendev.org/c/openstack/neutron/+/785830 Committed: https://opendev.org/openstack/neutron/commit/109faeac7e2e37da3bb7d5014a37ef18ed8cb80a Submitter: "Zuul (22348)" Branch:master commit 109faeac7e2e37da3bb7d5014a37ef18ed8cb80a Author: elajkat Date: Mon Apr 12 09:54:59 2021 +0200 trivial: Make driver_controller's _attrs_to_driver py3 compatible In python3 dict.values() doesn't return list but instead dict_values, it must be converted to list to "enjoy" list operations like insert. Add unit tests to be sure. Closes-Bug: #1923423 Change-Id: Ie270ac2ee65c02bdb099d11af7f1d2fb62ad0f61 ** Changed in: neutron Status: Triaged => 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/1923423 Title: l3_router.service_providers DriverController's _attrs_to_driver is not py3 compatible Status in neutron: Fix Released Bug description: Currently l3_router.service_providers.DriverController._attrs_to_driver has the following: ... drivers = self.drivers.values() # make sure default is tried before the rest if defined if self.default_provider: drivers.insert(0, self.drivers[self.default_provider]) As in python3 dict.values() gives back "dict_values" instead of list, insert will fail with: "AttributeError: 'dict_values' object has no attribute 'insert'" To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1923423/+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 1926170] [NEW] Sanity check should load SR-IOV agen config options
Public bug reported: If a config file is provided, SR-IOV agent config option "SRIOV_NIC.physical_device_mappings" should be loaded. If not, the error raised is: http://paste.openstack.org/show/804782/ ** Affects: neutron Importance: Low Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) ** Changed in: neutron Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1926170 Title: Sanity check should load SR-IOV agen config options Status in neutron: New Bug description: If a config file is provided, SR-IOV agent config option "SRIOV_NIC.physical_device_mappings" should be loaded. If not, the error raised is: http://paste.openstack.org/show/804782/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1926170/+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 1926219] [NEW] neutron command l3-agent-list-hosting-router and dhcp-agent-list-hosting-net don't exist in openstack client
Public bug reported: these two useful neutron cli command aren't in openstack client: (overcloud) [stack@undercloud-0 ~]$ neutron l3-agent-list-hosting-router tempest-router-2120132397 neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+--+ | id | host | admin_state_up | alive | ha_state | +--+---++---+--+ | 1ee45cf7-1aa6-47fc-aa21-4713dd3ae119 | networker-2.redhat.local | True | :-) | standby | | 2baa2189-8d27-4477-89b8-31afb4d7b1ba | networker-0.redhat.local | True | :-) | active | | 39ae6b11-a49a-4d85-9a8f-919416f4931e | controller-1.redhat.local | True | :-) | standby | +--+---++---+--+ (overcloud) [stack@undercloud-0 ~]$ neutron dhcp-agent-list-hosting-net nova neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+ | id | host | admin_state_up | alive | +--+---++---+ | 71befd34-b569-4d00-b6b5-d34266e5b33e | controller-0.redhat.local | True | :-) | | 77f6e7ee-1d37-4ab6-a805-455b2dbbf341 | networker-1.redhat.local | True | :-) | | 81638b13-95d0-43c1-be23-eb8422c00ce0 | controller-2.redhat.local | True | :-) | | 95bf9893-79b3-4f56-a6f2-653977e1700d | networker-2.redhat.local | True | :-) | | be3a478d-8ea7-4eca-9430-72b6e1a826d4 | controller-1.redhat.local | True | :-) | | dfd410b2-1fc0-4eb3-a383-583e37e810fb | networker-0.redhat.local | True | :-) | +--+---++---+ (overcloud) [stack@undercloud-0 ~]$ ** 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/1926219 Title: neutron command l3-agent-list-hosting-router and dhcp-agent-list- hosting-net don't exist in openstack client Status in neutron: New Bug description: these two useful neutron cli command aren't in openstack client: (overcloud) [stack@undercloud-0 ~]$ neutron l3-agent-list-hosting-router tempest-router-2120132397 neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+--+ | id | host | admin_state_up | alive | ha_state | +--+---++---+--+ | 1ee45cf7-1aa6-47fc-aa21-4713dd3ae119 | networker-2.redhat.local | True | :-) | standby | | 2baa2189-8d27-4477-89b8-31afb4d7b1ba | networker-0.redhat.local | True | :-) | active | | 39ae6b11-a49a-4d85-9a8f-919416f4931e | controller-1.redhat.local | True | :-) | standby | +--+---++---+--+ (overcloud) [stack@undercloud-0 ~]$ neutron dhcp-agent-list-hosting-net nova neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+ | id | host | admin_state_up | alive | +--+---++---+ | 71befd34-b569-4d00-b6b5-d34266e5b33e | controller-0.redhat.local | True | :-) | | 77f6e7ee-1d37-4ab6-a805-455b2dbbf341 | networker-1.redhat.local | True | :-) | | 81638b13-95d0-43c1-be23-eb8422c00ce0 | controller-2.redhat.local | True | :-) | | 95bf9893-79b3-4f56-a6f2-653977e1700d | networker-2.redhat.local | True | :-) | | be3a478d-8ea7-4eca-9430-72b6e1a826d4 | controller-1.redhat.local | True | :-) | | dfd410b2-1fc0-4eb3-a383-583e37e810fb | networker-0.redhat.local | True | :-) | +--+---++---+ (overcloud) [stack@undercloud-0 ~]$ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1926219/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https:/
[Yahoo-eng-team] [Bug 1883089] Re: [L3] floating IP failed to bind due to no agent gateway port(fip-ns)
** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Focal) 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/1883089 Title: [L3] floating IP failed to bind due to no agent gateway port(fip-ns) Status in neutron: Fix Released Status in neutron package in Ubuntu: New Status in neutron source package in Focal: New Bug description: In patch [1] it introduced a binding of DB uniq constraint for L3 agent gateway. In some extreme case the DvrFipGatewayPortAgentBinding is in DB while the gateway port not. The current code path only checks the binding existence which will pass a "None" port to the following code path that results an AttributeError. [1] https://review.opendev.org/#/c/702547/ Exception log: 2020-06-11 15:39:28.361 1285214 INFO neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port for network 3fcb7702-ae0b-46b4-807f-8ae94d656dd3 does not exist on host host-compute-1. Creating one. 2020-06-11 15:39:28.370 1285214 DEBUG neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port for network 3fcb7702-ae0b-46b4-807f-8ae94d656dd3 already exists on host host-compute-1. Probably it was just created by other worker. create_fip_agent_gw_port_if_not_exists /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:927 2020-06-11 15:39:28.390 1285214 DEBUG neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port None found for the destination host: host-compute-1 create_fip_agent_gw_port_if_not_exists /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:933 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Exception during message handling: AttributeError: 'NoneType' object has no attribute 'get' 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 170, in _process_incoming 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 220, in dispatch 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 190, in _do_dispatch 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/neutron/db/api.py", line 91, in wrapped 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server setattr(e, '_RETRY_EXCEEDED', True) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server self.force_reraise() 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/neutron/db/api.py", line 87, in wrapped 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_db/api.py", line 147, in wrapper 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server ectxt.value = e.inner_exc 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server self.force_reraise() 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_db/api.py", line 135, in wrappe
[Yahoo-eng-team] [Bug 1883089] Re: [L3] floating IP failed to bind due to no agent gateway port(fip-ns)
** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Impish) Status: New => Fix Released ** Changed in: neutron (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: neutron (Ubuntu Groovy) Status: New => Fix Released ** Tags added: sts -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1883089 Title: [L3] floating IP failed to bind due to no agent gateway port(fip-ns) Status in neutron: Fix Released Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Focal: New Status in neutron source package in Groovy: Fix Released Status in neutron source package in Hirsute: Fix Released Status in neutron source package in Impish: Fix Released Bug description: In patch [1] it introduced a binding of DB uniq constraint for L3 agent gateway. In some extreme case the DvrFipGatewayPortAgentBinding is in DB while the gateway port not. The current code path only checks the binding existence which will pass a "None" port to the following code path that results an AttributeError. [1] https://review.opendev.org/#/c/702547/ Exception log: 2020-06-11 15:39:28.361 1285214 INFO neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port for network 3fcb7702-ae0b-46b4-807f-8ae94d656dd3 does not exist on host host-compute-1. Creating one. 2020-06-11 15:39:28.370 1285214 DEBUG neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port for network 3fcb7702-ae0b-46b4-807f-8ae94d656dd3 already exists on host host-compute-1. Probably it was just created by other worker. create_fip_agent_gw_port_if_not_exists /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:927 2020-06-11 15:39:28.390 1285214 DEBUG neutron.db.l3_dvr_db [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Floating IP Agent Gateway port None found for the destination host: host-compute-1 create_fip_agent_gw_port_if_not_exists /usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py:933 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server [None req-d6a41187-2495-46bf-a424-ab7195c0ecb1 - - - - -] Exception during message handling: AttributeError: 'NoneType' object has no attribute 'get' 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 170, in _process_incoming 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 220, in dispatch 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 190, in _do_dispatch 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/neutron/db/api.py", line 91, in wrapped 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server setattr(e, '_RETRY_EXCEEDED', True) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server self.force_reraise() 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/neutron/db/api.py", line 87, in wrapped 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_db/api.py", line 147, in wrapper 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server ectxt.value = e.inner_exc 2020-06-11 15:39:28.391 1285214 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 22
[Yahoo-eng-team] [Bug 1926219] Re: neutron command l3-agent-list-hosting-router and dhcp-agent-list-hosting-net don't exist in openstack client
I just checked and it seems it is possible to do with OpenStack client with commands like: openstack network agent list --network private and openstack network agent list --router router1 ** Changed in: neutron Status: New => Invalid ** Changed in: neutron Assignee: (unassigned) => Slawek Kaplonski (slaweq) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1926219 Title: neutron command l3-agent-list-hosting-router and dhcp-agent-list- hosting-net don't exist in openstack client Status in neutron: Invalid Bug description: these two useful neutron cli command aren't in openstack client: (overcloud) [stack@undercloud-0 ~]$ neutron l3-agent-list-hosting-router tempest-router-2120132397 neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+--+ | id | host | admin_state_up | alive | ha_state | +--+---++---+--+ | 1ee45cf7-1aa6-47fc-aa21-4713dd3ae119 | networker-2.redhat.local | True | :-) | standby | | 2baa2189-8d27-4477-89b8-31afb4d7b1ba | networker-0.redhat.local | True | :-) | active | | 39ae6b11-a49a-4d85-9a8f-919416f4931e | controller-1.redhat.local | True | :-) | standby | +--+---++---+--+ (overcloud) [stack@undercloud-0 ~]$ neutron dhcp-agent-list-hosting-net nova neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--+---++---+ | id | host | admin_state_up | alive | +--+---++---+ | 71befd34-b569-4d00-b6b5-d34266e5b33e | controller-0.redhat.local | True | :-) | | 77f6e7ee-1d37-4ab6-a805-455b2dbbf341 | networker-1.redhat.local | True | :-) | | 81638b13-95d0-43c1-be23-eb8422c00ce0 | controller-2.redhat.local | True | :-) | | 95bf9893-79b3-4f56-a6f2-653977e1700d | networker-2.redhat.local | True | :-) | | be3a478d-8ea7-4eca-9430-72b6e1a826d4 | controller-1.redhat.local | True | :-) | | dfd410b2-1fc0-4eb3-a383-583e37e810fb | networker-0.redhat.local | True | :-) | +--+---++---+ (overcloud) [stack@undercloud-0 ~]$ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1926219/+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
