ovn-bgp-agent fails on startup if interface names > 16 symbols
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ovn-bgp-agent |
In Progress
|
High
|
Unassigned |
Bug Description
In cases, when a user does stupid thing and defines long enough interface names for bgp_vrf or bgp_nic, ovn-bgp-agent fails on startup early, as tries to re-create interface that's already existing.
Ie:
[DEFAULT]
....
bgp_vrf = BGP-LOOPBACK-
Will result on following stack trace on second restart:
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
2024-02-21 17:53:06.612 64903 ERROR oslo_service.
This happens because interface name is validly trimmed. However, when agent tries to ensure state, it's attempting to ensure it with invalid (long) name, and catches NetworkInterfac
But when create request is sent, it trimms network name and results in network existing:
Changed in ovn-bgp-agent: | |
importance: | Undecided → High |
Changed in ovn-bgp-agent: | |
status: | Fix Released → In Progress |
Fix proposed to branch: master /review. opendev. org/c/openstack /ovn-bgp- agent/+ /909788
Review: https:/