[ovn] mtu for metadata veth interface is not set
Bug #2053274 reported by
Mohammed Naser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Rodolfo Alonso |
Bug Description
When using OVN, the `veth` interfaces which get created inside the network namespace (and the other half that goes into the OVS bridge) both do not get an MTU configured for them when they are provisioned.
https:/
This can cause some unknown/annoying errors with packets being dropped if a user is hitting large requests on the metadata service, the ideal solution would be to configure the correct MTU for the interface to avoid this issue.
tags: | added: ovn |
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
To post a comment you must log in.
Can you add the failure/errors just so they are documented?
And have you tried setting it manually in the namespace and verified it helps?
It seems there is already a key for this, OVN_NETWORK_ MTU_EXT_ ID_KEY, but it's never set when a port is created in OVN NB from what I can tell. If that happened then the OVN metadata agent should be able to pull it out of the port binding in OVN SB when it gets the port info for its datapaths.
Most likely place to put that is in the ovn_client code in get_external_ ids_from_ port() and related functions, then modify the agent accordingly. Just my guess.