Re: [ovs-discuss] failed to put[create][modify]

2014-08-06 Thread Justin Pettit
Great to hear. Thanks for the confirmation! --Justin > On Aug 6, 2014, at 12:35 AM, Federico Iezzi wrote: > > Hi Guys! > > Good news, after 24 hours of tests nothing more errors! > I didn't finish all my test suite but usually I had errors immediately. > > Congratulations! > > Regards, > Fe

Re: [ovs-discuss] failed to put[create][modify]

2014-08-06 Thread Federico Iezzi
Hi Guys! Good news, after 24 hours of tests nothing more errors! I didn't finish all my test suite but usually I had errors immediately. Congratulations! Regards, Federico This email and any files transmitted with it are confidential and intended so

Re: [ovs-discuss] failed to put[create][modify]

2014-08-05 Thread Federico Iezzi
Hi Justine! Sure, I let you know during this day. Regards, Federico This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email

Re: [ovs-discuss] failed to put[create][modify]

2014-08-04 Thread Justin Pettit
On July 31, 2014 at 5:07:54 PM, Justin Pettit (jpet...@nicira.com) wrote: > On July 31, 2014 at 8:35:54 AM, Gurucharan Shetty (shet...@nicira.com) wrote: > > On Wed, Jul 30, 2014 at 4:49 PM, Jesse Gross wrote: > > > Thanks for running this with the extra logging. There is actually a > > > different

Re: [ovs-discuss] failed to put[create][modify]

2014-07-31 Thread Justin Pettit
On July 31, 2014 at 8:35:54 AM, Gurucharan Shetty (shet...@nicira.com) wrote: > On Wed, Jul 30, 2014 at 4:49 PM, Jesse Gross wrote: > > Thanks for running this with the extra logging. There is actually a > > different error code showing up now, so maybe that is progress :) > > > > I think Guru is c

Re: [ovs-discuss] failed to put[create][modify]

2014-07-30 Thread Federico Iezzi
Compiled and installed. So I’m running my test suite. I let you know something ASAP. Federico This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you

Re: [ovs-discuss] failed to put[create][modify]

2014-07-30 Thread Federico Iezzi
Sure! I let you know in the next couple of hours! Regards, Federico This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in

Re: [ovs-discuss] failed to put[create][modify]

2014-07-30 Thread Jesse Gross
The master branch actually has additional logging that was added to help debug this. Is it possible for you to try with this and share any messages you see in dmesg? On Wed, Jul 30, 2014 at 2:50 AM, Federico Iezzi wrote: > Hi Guys!! > > I’m sorry for this huge (!!|) delay but I was in vacation an

Re: [ovs-discuss] failed to put[create][modify]

2014-07-30 Thread Federico Iezzi
Hi Guys!! I’m sorry for this huge (!!|) delay but I was in vacation and when I came back I had to manage some trouble situations. So, this morning I test the latest 2.3 OVS version (commit 5eba2795fc5d4e833e9827ce18f6167e382bf0e1). OS Ubuntu 12.04.4 with Linux Kernel 3.13.0-32 provided by Canon

Re: [ovs-discuss] failed to put[create][modify]

2014-07-17 Thread Jesse Gross
If you are experiencing this problem, can you please test with the latest master code? It has a fix for one problem and additional logging in case there are others. On Tue, Jul 15, 2014 at 8:18 AM, yinpeijun wrote: > > Hi Jesse > > I want to know is there any conclusion or what is your next plan

Re: [ovs-discuss] failed to put[create][modify]

2014-07-17 Thread Jesse Gross
When we try to do ovs-dpctl dump-flows and grep for the MAC address > associated with the VMs, we see the flow has action set to drop. > Tcpdump on the tap interface of the VM' shows that it is sending DHCP > packets but the ovs bridge is dropping the flow. > > Vinay > >

Re: [ovs-discuss] failed to put[create][modify]

2014-07-15 Thread yinpeijun
Hi Jesse I want to know is there any conclusion or what is your next plan ? >Thanks for the additional information. > >I'm still having a hard time seeing how a flow could be invalid without >generating any log messages so I just sent out a patch to hopefully cover the >remaining cases (CC'e

Re: [ovs-discuss] failed to put[create][modify]

2014-07-08 Thread Jesse Gross
On Thu, Jul 3, 2014 at 10:34 PM, Bannai, Vinay wrote: > Hello Jesse, > > We are running a large Openstack deployment with several hundred > hypervisors running Openstack Havana with OVS. There are currently around > several thousand VM's running in this environment. > Here are the details: > > roo

Re: [ovs-discuss] failed to put[create][modify]

2014-07-01 Thread Jesse Gross
Thanks for the additional information. I'm still having a hard time seeing how a flow could be invalid without generating any log messages so I just sent out a patch to hopefully cover the remaining cases (CC'ed to you). The patch is against master - is it possible for you to try it and report any

Re: [ovs-discuss] failed to put[create][modify]

2014-06-30 Thread Federico Iezzi
Hi Jesse, Here we go, I’m really sorry for this huge delay but I had some trouble. So I tested all OVS version from 2.1.0 (under advise of Salvatore Orlando) to 2.3, all of this with kernel 3.11 to 3.13 and I had the following result. With Kernel 3.12 or 3.13 AND OVS 2.1 (datapath come from K

Re: [ovs-discuss] failed to put[create][modify]

2014-06-27 Thread Jesse Gross
On Thu, Jun 26, 2014 at 12:33 PM, Federico Iezzi wrote: > Eugene, > > The only way that I found is roll-back to a Kernel version < 3.12. > Today I did many tests with vanilla Kernel 3.11.10 and Canonical 3.11.0-24 I > haven't anymore problem using datapath from OVS source. I’m using VXLAN so I >

Re: [ovs-discuss] failed to put[create][modify] (Eugene Istomin)

2014-06-26 Thread Yinpeijun
>After implementing log parsing on some servers we discover the same issue (mac >are masked): > ><28>Jun 26 20:57:08 ovs-vswitchd: >ovs|207944|dpif(handler_1)|WARN|system@ovs-system: failed to >put[create][modify] (Invalid argument) >skb_priority(0),in_port(2),skb_mark(0/0),eth(src=XX,dst=ff:f

Re: [ovs-discuss] failed to put[create][modify]

2014-06-26 Thread Federico Iezzi
To: Jesse Gross Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] failed to put[create][modify] Jesse, our syslog rules covers all possible syslog-like logs (including kernel), i don't find any related messages (dmesg are clean too). --- Best regards, Eugene Isto

Re: [ovs-discuss] failed to put[create][modify]

2014-06-26 Thread Eugene Istomin
Jesse, our syslog rules covers all possible syslog-like logs (including kernel), i don't find any related messages (dmesg are clean too). /---/ */Best regards,/* /Eugene Istomin/ /EDS Systems/ /e.isto...@edss.ee/ /Work: +372-6409-600/ > On Thu, Jun 26, 2014 at 11:33 AM, Eugene Istomin wrote:

Re: [ovs-discuss] failed to put[create][modify]

2014-06-26 Thread Jesse Gross
On Thu, Jun 26, 2014 at 11:33 AM, Eugene Istomin wrote: > After implementing log parsing on some servers we discover the same issue > (mac are masked): > > > > <28>Jun 26 20:57:08 ovs-vswitchd: > ovs|207944|dpif(handler_1)|WARN|system@ovs-system: failed to > put[create][modify] (Invalid argument)

Re: [ovs-discuss] failed to put[create][modify]

2014-06-24 Thread Federico Iezzi
! Regards, Federico From: Joe Stringer [joestrin...@nicira.com] Sent: Wednesday, June 25, 2014 1:23 AM To: Federico Iezzi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] failed to put[create][modify] Is this with the kernel module upstream, or the version that you built from the tree

Re: [ovs-discuss] failed to put[create][modify]

2014-06-24 Thread Federico Iezzi
. Thanks a lot for your support! Regards, Federico ps: I'm sorry for the HTML version, it was my fault! From: Jesse Gross [je...@nicira.com] Sent: Tuesday, June 24, 2014 10:02 PM To: Federico Iezzi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] failed to put[create][m

Re: [ovs-discuss] failed to put[create][modify]

2014-06-24 Thread Federico Iezzi
Hi Jesse, Unfortunately I don’t have any other logs into dmesg, kern.log and syslog. The problem is that I have a big amount of packet loss and retransmission for 25% of time. So the OVS Rule for 75% time works. It seems like a overflow kind but I’m not capable of debugging C++ code anymore. Tha

Re: [ovs-discuss] failed to put[create][modify]

2014-06-24 Thread Jesse Gross
On Fri, Jun 20, 2014 at 8:01 AM, Federico Iezzi wrote: > Hi Guys, > > I’m in trouble with our staging OpenStack env based on IceHouse Neutron > and Havana Nova. > We are using Ubuntu 12.04.4 with Kernel 3.13 mirror release 11. > > With the latests OVS versione (2.1.2, 2.1.3, 2.2.0 and 2.3 DEV