When an OVSDB node is passively connected to the OVSDB plugin (i.e. the node initiates the connection to ODL), updates to the OVSDB node fail due to lack of connection-info information in the MD-SAL config.

It is possible to configure bridge nodes and ports (termination-points) to a passively connected OVSDB node, so the issue is specifically with configuring the OVSDB node itself.

A workaround is to supply connection-info to the OVSDB node config, but this requires looking up the remote tcp ephemeral port number for the connection. This is not desired - all of the required information is provided in the URL (e.g. the node-id for the OVSDB node).