Description of problem:

The ovnkube-node and onvkube-controller is failing with the error:

~~~
2026-03-09T22:50:47.419982684Z + exec /usr/bin/ovnkube --init-ovnkube-controller <host> --init-node <host> --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4 --inactivity-probe=180000 --gateway-mode shared --gateway-interface br-ex --metrics-bind-address 127.0.0.1:29103 --ovn-metrics-bind-address 127.0.0.1:29105 --metrics-enable-pprof --metrics-enable-config-duration --export-ovs-metrics --disable-snat-multiple-gws --enable-multi-network --enable-network-segmentation --enable-preconfigured-udn-addresses --enable-admin-network-policy --enable-multicast --zone <host> --enable-interconnect --acl-logging-rate-limit 20 --disable-forwarding --bootstrap-kubeconfig=/var/lib/kubelet/kubeconfig --cert-dir=/etc/ovn/ovnkube-node-certs --cert-duration=24h --gateway-v4-masquerade-subnet 169.254.0.0/17 --gateway-v6-masquerade-subnet fd69::/112 --enable-egress-ip=true --enable-egress-firewall=true --enable-egress-qos=true --enable-egress-service=true --enable-multi-external-gateway=true

2026-03-09T22:50:47.425883274Z panic: runtime: allocation size out of range
~~~

We are not sure why this happened.
We are currently checking the `oc debug ds/ovnkube-node ...` to see if we are getting the same error.

This is blocking the cluster to start as CNI is not configured on the node.
This is SNO node.

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

OpenShift Container Platform 4.20.11
SNO

How reproducible:
n/a

Steps to Reproduce:

1.

2.

3.

Actual results:

Expected results:

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms: