> Hi all,
> 
> I’m running ovn 20.06.2 with ovs 2.13.0. On some nodes in ovs-vswitchd.log I 
> see lots of warnings like this:
> 
> 2021-03-09T05:05:57.349Z|00062|dpif(handler3)|WARN|system at ovs-system: 
> execute ct(commit,zone=58,label=0/0x1),33 failed (Invalid argument) on packet 
> icmp,vlan_tci=0x0000,dl_src=<MAC1>,dl_dst=<MAC2>,nw_src=<IP1>,nw_dst=<IP2>,nw_tos=0,nw
> _ecn=0,nw_ttl=52,icmp_type=8,icmp_code=0 icmp_csum:e827
> with metadata 
> skb_priority(0),tunnel(tun_id=0x20009000010,src=<IP3>,dst=<IP4>,ttl=61,tp_src=37080,tp_dst=7471,flags(csum|key)),skb_mark(0),ct_state(0x21),ct_zone(0x3a),ct_tuple4(src=220.242.181.108,dst=192.168.0.5,proto=1,tp_src=8,tp_dst=0),in_port(2)
>  mtu 0

Hi.  Not sure if you already figured out the root cause, but
this looks very similar to the issue fixed by:
  
https://patchwork.kernel.org/project/netdevbpf/patch/[email protected]/

> 
> How can I understand which argument is exactly invalid and what could be the 
> reason?

Unfortunately, it's not possible right now, so debugging is tricky.
There is a plan to receive meaningful error messages from the kernel via
netlink and print them in logs, but this is not implemented yet.

Best regards, Ilya Maximets.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to