Comment 3 for bug 1955008

The ovsdb error is stopping the test:
2022-01-23 19:28:46.875 54853 ERROR ovsdbapp.backend.ovs_idl.vlog [-] tcp:127.0.0.1:42597: error parsing update: ovsdb error: Modify non-existing row: ovs.db.error.Error: ovsdb error: Modify non-existing row

After this line, the test is just stopping the controllers and the DB servers.

I think we should implement [1] but for all FT tests, that means in "TestOVNFunctionalBase" and not only for the NB but for the SB too. In the DB log I see the connection is updated AFTER the network creation command "network1" has been committed:
2022-01-23T19:28:46.868Z|00156|jsonrpc|DBG|tcp:127.0.0.1:33296: send notification, method="update2", params=["ae7bd9c6-7c82-11ec-9a03-4fce359daaf8",{"Connection":{"83c29962-a6e2-4f3c-9fc7-888cf46540ed":{"modify":{"is_connected":true,"status":["map",[["bound_port","42597"],["n_connections","2"],["sec_since_connect","0"],["sec_since_disconnect","0"]]]}}},"Datapath_Binding":{"15003f80-2b91-44d6-8b9d-f8d217285fb3":{"insert":{"tunnel_key":1,"external_ids":["map",[["logical-switch","70caa880-3fed-4f9b-9558-f624c0d2c469"],["name","neutron-51ac15e4-24cc-4348-85c3-fe3a51cfcaec"],["name2","network1"]]]}}}}]

In any case, what I think is failing is the connection to the OVS DB, not the NB or SB DBs.

[0]https://review.opendev.org/q/Id84bf17953527c415d611bfc198038fb6f811de3
[1]https://review.opendev.org/c/openstack/neutron/+/825530/8/neutron/tests/functional/plugins/ml2/drivers/ovn/mech_driver/ovsdb/test_ovn_db_resources.py#32