On Wed, Jun 20, 2018 at 10:44:51AM +0300, Ilya Maximets wrote: > Recent assertion failure fix changed rconn workflow for unreliable > connections (such as connections from ovs-ofctl) from > > |rconn|DBG|br-int<->unix#151: entering ACTIVE > |rconn|DBG|br-int<->unix#151: connection closed by peer > |rconn|DBG|br-int<->unix#151: entering DISCONNECTED > > To > > |rconn|DBG|br-int<->unix#200: entering CONNECTING > |rconn|INFO|br-int<->unix#200: connected > |rconn|DBG|br-int<->unix#200: entering ACTIVE > |rconn|DBG|br-int<->unix#200: connection closed by peer > |rconn|DBG|br-int<->unix#200: entering DISCONNECTED > > Many monitoring/configuring tools (ex. ovs-neutron-agent) uses > ovs-ofctl frequently to check the statuses of installed flows. > This produces a lot of "connected" logs, that are useless in general. > > Fix that by changing the log level to DBG for unreliable connections. > > Suggested-by: Ben Pfaff <[email protected]> > Fixes: c9a9b9b00bf5 ("rconn: Introduce new invariant to fix assertion > failure in corner case.") > Signed-off-by: Ilya Maximets <[email protected]>
I applied this to master and backported as far as branch-2.5. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
