On Sat, Dec 12, 2015 at 04:32:44PM +0530, Numan Siddique wrote: > I investigated a little bit and found the reason for the Broken pipe error > logs which we see in ovsdb-server.log for some of the ovn test cases. > > In my testing, I observed the issue for below sequence > - test case calls "ovn-nbctl lport-add br-test vif0" > > - ovn-northd detects this change and updates the ovn-nb with up=false for > vif0. > > - ovn-nbctl closes the connection to the ovsdb-server > > - ovsdb-server sends monitor update command for "vif0" > [ovsdb_jsonrpc_monitor_flush_all(s) called by ovsdb_jsonrpc_session_run] to > the ovn-nbctl even though ovn-nbctl has closed the connection and hence the > send fails with broken pipe error. > > > Not sure, it this issue needs to be handled by ovsdb-server/ovn-nbctl.
I think it's probably reasonable to just ignore "broken pipe" errors in the ovsdb-server log, at least in test cases that involve OVN and possibly elsewhere. (ovs-vsctl could cause the same errors, I guess, if it is invoked with --no-wait, but most of the time in the testsuite we don't use that option.) _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
