external_gateways KeyError when running add_gw_port_info_to_logical_router_port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Committed
|
High
|
Brian Haley |
Bug Description
Version: 2023.1
Driver: OVN
I'm seeing the following error:
```
Failed to call periodic 'neutron.
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics Traceback (most recent call last):
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics File "/var/lib/
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics work()
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics File "/var/lib/
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics return self.callback(
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics File "/var/lib/
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics return f(*args, **kwargs)
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics File "/var/lib/
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics ext_gw[
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics KeyError: 'external_gateways'
2024-03-14 14:37:08.974 1026 ERROR futurist.periodics
```
This is triggered every ten minutes. Does the external_gateways field only exist if you have the external-
Changed in neutron: | |
assignee: | nobody → Brian Haley (brian-haley) |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
status: | In Progress → Fix Committed |
Looks like you are correct about the issue, the multiple gateway support was added in 2032.2 in [0] so the backport you mention should have been modified when it was cherry-picked to 2023.1, it needs to get the external gateway from the router object something like:
router. get(l3. EXTERNAL_ GW_INFO)
but that code in the maintenance task will need more tweaking than that, and we need to make sure there is a test since it should have failed our gate tests.
[0] https:/ /review. opendev. org/c/openstack /neutron/ +/873593