Comment 2 for bug 1734090

I also sent this patch [0] to have functional test logs in networking-ovn.
Looks like the connection to ovsdb is lost (some crash?) [1] and then we're failing
to connect again. As we're starting ovsdb-server in the test, if it crashes
we're not going to recover. Why it fails is still unknown to me but I'll try to
dig further to see if it crashes at some point and why.

2017-11-23 12:04:39.378 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:45997: connection closed by peer
2017-11-23 12:04:39.379 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:35722: connection closed by peer
2017-11-23 12:04:39.379 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:45997: connection closed by peer
2017-11-23 12:04:39.379 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:35722: connection closed by peer
2017-11-23 12:04:39.380 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:35722: connection closed by peer
2017-11-23 12:04:39.380 24566 INFO ovsdbapp.backend.ovs_idl.vlog [-] ssl:127.0.0.1:45997: connection closed by peer

[0] https://review.openstack.org/#/c/522528/
[1] http://logs.openstack.org/28/522528/1/check/networking-ovn-dsvm-functional/ff0ad9a/logs/dsvm-functional-logs/networking_ovn.tests.functional.test_ovn_db_sync.TestOvnNbSyncOverSsl.test_ovn_nb_sync_repair.txt.gz#_2017-11-23_12_04_39_378