Comment 3 for bug 1817022

The bug description mixes two distinct connection types:
1. the manager connection for ovsdb: ovs-agent<->ovsdb-server:6640.
2. the per bridge openflow controller connection: ovs-vswitchd<->ovs-agent:6633

The inactivity_probe for the first should already be configurable with this patch:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1698bee770b84a2663ba940a6ded5d4b9733101a

For reference, http://www.openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.html
Controller TABLE
...
     Controller Failure Detection and Handling:

       max_backoff: optional integer, at least 1,000
              Maximum number of milliseconds to wait between connection at‐
              tempts. Default is implementation-specific.

       inactivity_probe: optional integer
              Maximum number of milliseconds of idle time on connection to
              controller before sending an inactivity probe message. If Open
              vSwitch does not communicate with the controller for the speci‐
              fied number of seconds, it will send a probe. If a response is
              not received for the same additional amount of time, Open
              vSwitch assumes the connection has been broken and attempts to
              reconnect. Default is implementation-specific. A value of 0 dis‐
              ables inactivity probes.

When they are not set, `ovs-vsctl --columns=_uuid,inactivity_probe,max_backoff list controller` shows them as '[]', and OVS defaults to 5000ms for inactivity_probe, and 8000ms for max_backoff.