-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
Important
-
None
Description of problem:
Our localnet example does not include the MTU attribute. That is problematic, since the OVN localnet default is 1400, while the standard value would be 1500. This leads to situations where customers suffer packet loss without any understanding what may be wrong (they assume their MTU is 1500 everywhere).
Version-Release number of selected component (if applicable):
4.15+
How reproducible:
Always
Steps to Reproduce:
1. Go to https://docs.redhat.com/en/documentation/openshift_container_platform/4.15/html/virtualization/networking#virt-creating-localnet-nad-cli_virt-connecting-vm-to-ovn-secondary-network 2. See the NAD example
Actual results:
{ "cniVersion": "0.3.1", 1 "name": "localnet-network", 2 "type": "ovn-k8s-cni-overlay", 3 "topology": "localnet", 4 "netAttachDefName": "default/localnet-network" 5 }
Expected results:
{ "cniVersion": "0.3.1", 1 "name": "localnet-network", 2 "type": "ovn-k8s-cni-overlay", 3 "topology": "localnet", 4 "mtu": 1500, 5 "netAttachDefName": "default/localnet-network" 6 }
Additional info:
- is related to
-
CNV-59629 Localnet UI dialog should set an explicit MTU
-
- MODIFIED
-
- relates to
-
OCPBUGS-54739 localnet networks default to overlay MTU value
-
- ASSIGNED
-