Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1931674

Summary: [Kuryr] Enforce nodes MTU for the Namespaces and Pods
Product: OpenShift Container Platform Reporter: Maysa Macedo <mdemaced>
Component: NetworkingAssignee: Maysa Macedo <mdemaced>
Networking sub component: kuryr QA Contact: Itzik Brown <itbrown>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: medium CC: juriarte, mdulko
Version: 4.6.z   
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1932113 (view as bug list) Environment:
Last Closed: 2021-07-27 22:47:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1932113    

Description Maysa Macedo 2021-02-22 22:09:30 UTC 
Description of problem:

The MTU value used on the Nodes Network should also be used for the Namespace Network and Pods VIF to avoid any possible MTU misconfiguration on a cluster that is already running.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Maysa Macedo 2021-02-24 01:43:39 UTC 
The fixes for this bug are already present on master so I'm moving it to ON_QA.

https://github.com/openshift/kuryr-kubernetes/commit/17f99a71782caec0cbf73cb268fc55ef0d2dba06
https://github.com/openshift/cluster-network-operator/commit/a918dd93e3059dc53c9f5d786fecc1ef5f56955c
Comment 3 Itzik Brown 2021-04-20 08:08:28 UTC 
Checked with: 
RHOS-16.1-RHEL-8-20210323.n.0
OCP 4.8.0-0.nightly-2021-04-18-101412

Using a tenant:
Create a network with MTU 1400 and a subnet
(shiftstack) [cloud-user@installer-host ~]$ openstack network show net1 |grep mtu
| mtu                       | 1400        

Created a router and added to the router as well as setting the gateway

Checked the MTU of the openshift-kuryr-net

(shiftstack) [cloud-user@installer-host ~]$ openstack network show ns/openshift-kuryr-net | grep mtu
| mtu                       | 1400   

Checked one of the pods MTU
(shiftstack) [cloud-user@installer-host ~]$ oc exec -it packageserver-5d69b87476-slkp4 -n openshift-operator-lifecycle-
manager -- ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000                           
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
19: eth0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default qlen 1000               
    link/ether fa:16:3e:3c:30:93 brd ff:ff:ff:ff:ff:ff link-netnsid 0                                                 
    inet 10.128.14.208/23 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe3c:3093/64 scope link
       valid_lft forever preferred_lft forever
Comment 6 errata-xmlrpc 2021-07-27 22:47:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438