On Mon, Aug 12, 2019 at 7:35 PM Darrell Ball <[email protected]> wrote: > > Thanks for the patch > > Not a full review; I just did a quick run of the test using a more recent > kernel version > > dball@ubuntu:~/ovs$ uname -r > 5.0.0-23-generic > dball@ubuntu:~/ovs$ lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 18.04.3 LTS > Release: 18.04 > Codename: bionic > > The test is no longer blocked on subsequent runs, at least with this kernel > version (others: TBD) - cool ! > > However > > ## ------------------------------- ## > ## openvswitch 2.12.90 test suite. ## > ## ------------------------------- ## > 75: conntrack - zone-based timeout policy FAILED > (system-traffic.at:3228) > > . > . > . > VSCTL_ADD_ZONE_TIMEOUT_POLICY([zone=5 udp_single=3 icmp_first=3]) > > dnl Send ICMP and UDP traffic > NS_CHECK_EXEC([at_ns0], [ping -q -c 3 -i 0.3 -w 2 10.1.1.2 | FORMAT_PING], > [0], [dnl <<<<<<<<<<<<<<<<<<<<< FAILS HERE > 3 packets transmitted, 3 received, 0% packet loss, time 0ms > ]) > . > . > . > > -3 packets transmitted, 3 received, 0% packet loss, time 0ms > +7 packets transmitted, 0 received, 100% packet loss, time 0ms > > warnings: > > > 2019-08-13T02:19:06.674Z|00001|dpif(handler1)|WARN|system@ovs-system: > > failed to put[create] (Invalid argument) > > ufid:55d8603a-729c-43d7-9612-b54553e46299 > > recirc_id(0x2),dp_hash(0/0),skb_priority(0/0),in_port(2),skb_mark(0/0),ct_state(0x21/0x23),ct_zone(0x5/0),ct_mark(0/0),ct_label(0/0),ct_tuple4(src=10.1.1.1/0.0.0.0,dst=10.1.1.2/0.0.0.0,proto=1/0,tp_src=8/0,tp_dst=0/0),eth(src=8a:ea:c3:02:6f:94/00:00:00:00:00:00,dst=92:48:5b:47:e2:63/00:00:00:00:00:00),eth_type(0x0800),ipv4(src=10.1.1.1/0.0.0.0,dst=10.1.1.2/0.0.0.0,proto=1,tos=0/0,ttl=64/0,frag=no),icmp(type=8/0,code=0/0), > > actions:ct(commit,zone=5,timeout=ovs_tp_0_icmp4),3 > > 2019-08-13T02:19:06.674Z|00002|dpif(handler1)|WARN|system@ovs-system: > > execute ct(commit,zone=5,timeout=ovs_tp_0_icmp4),3 failed (Invalid > > argument) on packet > > icmp,vlan_tci=0x0000,dl_src=8a:ea:c3:02:6f:94,dl_dst=92:48:5b:47:e2:63,nw_src=10.1.1.1,nw_dst=10.1.1.2,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_type=8,icmp_code=0 > > icmp_csum:4d0a > > with metadata > > skb_priority(0),skb_mark(0),ct_state(0x21),ct_zone(0x5),ct_tuple4(src=10.1.1.1,dst=10.1.1.2,proto=1,tp_src=8,tp_dst=0),in_port(2) > > mtu 0 > > 2019-08-13T02:19:06.999Z|00003|dpif(handler1)|WARN|system@ovs-system: > > failed to put[create] (Invalid argument) > > ufid:55d8603a-729c-43d7-9612-b54553e46299 > > recirc_id(0x2),dp_hash(0/0),skb_priority(0/0),in_port(2),skb_mark(0/0),ct_state(0x21/0x23),ct_zone(0x5/0),ct_mark(0/0),ct_label(0/0),ct_tuple4(src=10.1.1.1/0.0.0.0,dst=10.1.1.2/0.0.0.0,proto=1/0,tp_src=8/0,tp_dst=0/0),eth(src=8a:ea:c3:02:6f:94/00:00:00:00:00:00,dst=92:48:5b:47:e2:63/00:00:00:00:00:00),eth_type(0x0800),ipv4(src=10.1.1.1/0.0.0.0,dst=10.1.1.2/0.0.0.0,proto=1,tos=0/0,ttl=64/0,frag=no),icmp(type=8/0,code=0/0), > > actions:ct(commit,zone=5,timeout=ovs_tp_0_icmp4),3 > > 2019-08-13T02:19:06.999Z|00004|dpif(handler1)|WARN|system@ovs-system: > > execute ct(commit,zone=5,timeout=ovs_tp_0_icmp4),3 failed (Invalid > > argument) on packet > > icmp,vlan_tci=0x0000,dl_src=8a:ea:c3:02:6f:94,dl_dst=92:48:5b:47:e2:63,nw_src=10.1.1.1,nw_dst=10.1.1.2,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_type=8,icmp_code=0 > > icmp_csum:2f10 > > with metadata > > skb_priority(0),skb_mark(0),ct_state(0x21),ct_zone(0x5),ct_tuple4(src=10.1.1.1,dst=10.1.1.2,proto=1,tp_src=8,tp_dst=0),in_port(2) > > mtu 0
Thanks for trying this test out on the other setup. The warning messages indicate that the kernel module does not understand the new added ct timeout action attribute. I am wondering if the system used the correct kernel module? Can you check 'modinfo openvswitch' and 'dmesg' to make sure the correct kernel module is loaded in the system? Thanks, -Yi-Hung _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
