Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-07 Thread Lance Richardson
- Original Message - > From: "Justin Pettit" > To: "Lance Richardson" > Cc: dev@openvswitch.org > Sent: Thursday, July 7, 2016 5:25:52 PM > Subject: Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl > state machine > > >

Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-07 Thread Justin Pettit
> On Jul 5, 2016, at 5:58 AM, Lance Richardson wrote: > > --- a/ovn/controller/ofctrl.c > +++ b/ovn/controller/ofctrl.c > @@ -410,36 +410,36 @@ ofctrl_run(const struct ovsrec_bridge *br_int) > default: > OVS_NOT_REACHED(); > } > -} while (state != old_state); > >

Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-05 Thread Lance Richardson
- Original Message - > From: "Ryan Moats" > To: "Lance Richardson" > Cc: dev@openvswitch.org > Sent: Tuesday, July 5, 2016 12:17:17 PM > Subject: Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl > statemachine >

Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-05 Thread Ryan Moats
"dev" wrote on 07/05/2016 07:58:24 AM: > From: Lance Richardson > To: dev@openvswitch.org > Date: 07/05/2016 07:58 AM > Subject: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl > state machine > Sent by: "dev" > > The "ovn -- 2 H

Re: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-05 Thread Lance Richardson
- Original Message - > From: "Lance Richardson" > To: dev@openvswitch.org > Sent: Tuesday, July 5, 2016 8:58:24 AM > Subject: [ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state > machine > > The "ovn -- 2 HVs, 3 LRs connecte

[ovs-dev] [PATCH] ovn-controller: eliminate stall in ofctrl state machine

2016-07-05 Thread Lance Richardson
The "ovn -- 2 HVs, 3 LRs connected via LS, static routes" test case currently exhibits frequent failures. These failures occur because, at the time that the test packets are sent to verify forwarding, no flows have been installed in the vswitch for one of the hypervisors. Investigation shows that,