Skip to content

Missing verifier logs in Cilium logs #20738

@pchaigno

Description

@pchaigno

The new loader doesn't give us very useful logs when hitting a verifier error:

level=debug msg="Error regenerating endpoint: error loading eBPF collection into the kernel: program handle_lxc_traffic: load program: argument list too long: 2069: (55) if r8 != 0x0 goto pc-727: R0=inv,min_value=0,max_v (truncated, 26014 line(s) omitted) (BTF disabled)" code=Failure containerID= datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=1044 endpointState=ready identity=1 ipv4= ipv6= k8sPodName=/ policyRevision=0 subsys=endpoint type=200
level=error msg="endpoint regeneration failed" containerID= datapathPolicyRevision=0 desiredPolicyRevision=1 endpointID=1044 error="error loading eBPF collection into the kernel: program handle_lxc_traffic: load program: argument list too long: 2069: (55) if r8 != 0x0 goto pc-727: R0=inv,min_value=0,max_v (truncated, 26014 line(s) omitted) (BTF disabled)" identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint

Likely caused by #19159.

Metadata

Metadata

Assignees

Labels

area/loaderImpacts the loading of BPF programs into the kernel.kind/bugThis is a bug in the Cilium logic.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions