yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #93622
[Bug 2053274] Re: [ovn] mtu for metadata veth interface is not set
Reviewed: https://review.opendev.org/c/openstack/neutron/+/909684
Committed: https://opendev.org/openstack/neutron/commit/47b4d14955451c320ce612e4e2e7d0a896e2fe36
Submitter: "Zuul (22348)"
Branch: master
commit 47b4d14955451c320ce612e4e2e7d0a896e2fe36
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Wed Feb 21 15:34:13 2024 +0000
[OVN] Set MTU of the VETH interfaces between OVS and metadata
The VETH pair between the metadata namespace and the local OVS now
has the same MTU as the network associated to this metadata service.
The "LSP.external_ids" field has a new key defined: "neutron:mtu".
This is the value of the network MTU.
This patch does not update the previous metadata datapaths nor the
existing LSP. This change will affect only to new created ports
and the corresponding metadata datapaths.
Closes-Bug: #2053274
Change-Id: I7ff300e9634e5e3fc68d70540392109fd8b9babc
** 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/2053274
Title:
[ovn] mtu for metadata veth interface is not set
Status in neutron:
Fix Released
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://github.com/openstack/neutron/blob/stable/zed/neutron/agent/ovn/metadata/agent.py#L589-L594
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2053274/+subscriptions
References