[ovs-discuss] Failure testing OVS-2.3, cannot ping between hosts after upgrade

[Justin Pettit]

On August 13, 2014 at 10:57:05 PM, Srini Seetharaman (srini.seetharaman at gmail.com) wrote:

> *$ tail -2 /var/log/openvswitch/ovs-vswitchd.log*
> 2014-08-14T05:52:52.803Z|00583|dpif(handler81)|WARN|system at ovs-system:
> failed to put[create] (Invalid argument)
> skb_priority(0),in_port(2),skb_mark(0/0),eth(src=00:00:00:00:00:01,dst=00:00:00:00:00:02),eth_type(0x0800),ipv4(src=10.0.0.1,dst=10.0.0.2,proto=1,tos=0,ttl=64,frag=no),icmp(type=8,code=0),  
> actions:push_mpls(label=100,tc=0,ttl=64,bos=1,eth_type=0x8847),1
> 2014-08-14T05:52:53.803Z|00585|dpif(handler81)|WARN|system at ovs-system:
> failed to put[create] (Invalid argument)
> skb_priority(0),in_port(2),skb_mark(0/0),eth(src=00:00:00:00:00:01,dst=00:00:00:00:00:02),eth_type(0x0800),ipv4(src=10.0.0.1,dst=10.0.0.2,proto=1,tos=0,ttl=64,frag=no),icmp(type=8,code=0),  
> actions:push_mpls(label=100,tc=0,ttl=64,bos=1,eth_type=0x8847),1

Can you run "ovs-dpctl dump-flows" while these messages are being logged?  Do you see anything flow-related in dmesg?  I can see these errors are preventing flows from being inserted into the kernel, but I'd still expect the traffic to be forwarded based on the userspace logic.

Simon, I haven't played with the MPLS features yet.  Would you expect this to work?

--Justin