Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenShift: OVN MTU problems #788

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

Akrog
Copy link
Contributor

@Akrog Akrog commented Feb 26, 2025

In some cases when deploying in baremetal we can see that ovnkube-controller fails to run with following error:

F0225 17:50:08.720752   34371 ovnkube.go:136] failed to run ovnkube: failed to start network controller: failed to start default network controller - while waiting for any node to have zone: "devin01.rhos.lab.eng.brq2.redhat.com.141.37.10.in-addr.arpa", error: context canceled
failed to start node network controller: failed to start default node network controller: interface MTU (1500) is too small for specified overlay MTU (1558)

We can see in etc that the MTU is set to 1500 instead of the default 1400:

$ sudo crictl exec -it $(sudo crictl ps |grep etcdctl | cut -f1 -d' ') etcdctl get /kubernetes.io/operator.openshift.io/networks/cluster | tail -n2 | jq .|grep mtu
                "f:mtu": {},
                "f:mtu": {}
        "mtu": 1500,

This patch fixes this problem by ensure we always use file 99-ovn.yaml to force the MTU.

In some cases when deploying in baremetal we can see that
ovnkube-controller fails to run with following error:

```
F0225 17:50:08.720752   34371 ovnkube.go:136] failed to run ovnkube: failed to start network controller: failed to start default network controller - while waiting for any node to have zone: "devin01.rhos.lab.eng.brq2.redhat.com.141.37.10.in-addr.arpa", error: context canceled
failed to start node network controller: failed to start default node network controller: interface MTU (1500) is too small for specified overlay MTU (1558)
```

We can see in etc that the MTU is set to 1500 instead of the default
1400:

```
$ sudo crictl exec -it $(sudo crictl ps |grep etcdctl | cut -f1 -d' ') etcdctl get /kubernetes.io/operator.openshift.io/networks/cluster | tail -n2 | jq .|grep mtu
                "f:mtu": {},
                "f:mtu": {}
        "mtu": 1500,
```

This patch fixes this problem by ensure we always use file `99-ovn.yaml`
to force the MTU.
@karmab karmab force-pushed the main branch 3 times, most recently from a669f76 to bfa7a03 Compare March 1, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant