OCP CI failed to attach XDP to ocp's node virtio interface

[msherif1234]

1.661178512849118e+09	INFO	controllers.IngressNodeFirewall	Comparing currently managed interfaces against list of XDP interfaces on system	{"e.managedInterfaces": {}}
1.6611785128495898e+09	INFO	controllers.IngressNodeFirewall	Attaching firewall interface	{"intf": "enp2s0"}
1.6611785128498745e+09	ERROR	controllers.IngressNodeFirewall	Fail to attach ingress firewall prog	{"error": "could not attach XDP program: can't create link: cannot allocate memory", "errorCauses": [{"error": "could not attach XDP program: can't create link: cannot allocate memory"}]}

[msherif1234]

https://coreos.slack.com/archives/C02G6GF5GKG/p1661181229836119
full log
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_release/31444/rehearse-31444-pull-ci-openshift-ingress-node-firewall-master-ingress-node-firewall-e2e-metal-ipi/1561702941142814720/artifacts/ingress-node-firewall-e2e-metal-ipi/gather-extra/artifacts/pods/openshift-ingress-node-firewall_ingress-node-firewall-daemon-zzhkl_daemon.log

[msherif1234]

Error is coming from here in cilium
https://github.com/cilium/ebpf/blob/eb74eecf3f5cd537c49e5eb326d80b59f4e885d0/link/link.go#L180
this is where ENOMEM is returned when attach XDP to interface
https://elixir.bootlin.com/linux/latest/source/net/core/dev.c#L9429

[msherif1234]

node journal shows

Aug 22 14:28:32.880306 worker-0.ostest.test.metalkube.org kernel: Adding Red Hat flag eBPF/xdp.
Aug 22 14:28:32.880528 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:32.880982 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:32.886388 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:32.907746 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:32.948781 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:33.030743 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:33.191752 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:33.512742 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:34.154759 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1
Aug 22 14:28:35.436762 worker-0.ostest.test.metalkube.org kernel: virtio_net virtio1 enp2s0: request 5 queues but max is 1

[msherif1234]

The following bz will bring in virtio kernel fix
https://bugzilla.redhat.com/show_bug.cgi?id=2122225

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[msherif1234]

OCP4.13 running RHEL9 should have the fix for this issue