This test intentionally configures an unreachable controller. It ignored
some error messages in the log, specifically
br0: cannot find route for controller (240.0.0.1): ...
but a bug report says that other forms of messages can also appear, e.g.
br0<->tcp:240.0.0.1:6653: connection dropped (No route to host)
This commit therefore expands the logged error messages that will be
ignored to any message that includes the IP address 240.0.0.1.
Reported-by: "Kurek, Tytus" <Tytus.Kurek@pega.com>
Reported-at: http://openvswitch.org/pipermail/discuss/2015-September/018910.html
Signed-off-by: Ben Pfaff <blp@nicira.com>
Acked-by: Justin Pettit <jpettit@nicira.com>
Thomas Morin thomas.morin@orange.com
Timothy Chen tchen@nicira.com
Torbjorn Tornkvist kruskakli@gmail.com
+Tytus Kurek Tytus.Kurek@pega.com
Valentin Bud valentin@hackaserver.com
Vasiliy Tolstov v.tolstov@selfip.ru
Vasu Dasari vdasari@gmail.com
}
(head_table classifier; ditto 1 253) > expout
AT_CHECK([ovs-ofctl dump-tables br0], [0], [expout])
-OVS_VSWITCHD_STOP(["/cannot find route for controller/d"])
+OVS_VSWITCHD_STOP(["/240\.0\.0\.1/d"])
AT_CLEANUP
AT_SETUP([ofproto - flow table configuration (OpenFlow 1.2)])