-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
-
Important
-
None
Description of problem:
The implicit default for MTU with OVN localnet is 1400. That is counterintuitive for network-savvy users who expect the default to be 1500. That leads to situations when a customer observes packet loss due to fragmentation, but is unable to spot an invalid configuration.
Version-Release number of selected component (if applicable):
4.15+ (not entirely sure when was the localnet UI introduced)
How reproducible:
Always
Steps to Reproduce:
1. Create a new NAD with the localnet topology, without setting any MTU 2. Look at the YAML
Actual results:
... spec: config: |- { "cniVersion": "0.4.0", "name": "physname", "type": "ovn-k8s-cni-overlay", "netAttachDefName": "phoracek/net1", "topology": "localnet" }
Expected results:
... spec: config: |- { "cniVersion": "0.4.0", "name": "physname", "type": "ovn-k8s-cni-overlay", "netAttachDefName": "phoracek/net1", "mtu": 1500, "topology": "localnet" }
Additional info:
The UI should require the MTU attribute to be set explicitly, defaulting it text field to 1500.
- relates to
-
CNV-59628 MTU attribute of OVN localnet should be a part of our examples
-
- New
-
-
OCPBUGS-54739 localnet networks default to overlay MTU value
-
- ASSIGNED
-
- links to