[ovn]Set NB/SB connection inactivity_probe does not work for cluster

[ZhouHeng]

If ovn is single node, we set config like:
[ovn]
ovn_nb_connection = tcp:100.2.223.2:6641
ovn_sb_connection = tcp:100.2.223.2:6642
The NB/SB connection inactivity_probe can be set correctly.

When ovn is in cluster deployment, config like:

[ovn]
ovn_nb_connection = tcp:100.2.223.2:6641,tcp:100.2.223.12:6641,tcp:100.2.223.30:6641
ovn_sb_connection = tcp:100.2.223.2:6642,tcp:100.2.223.12:6642,tcp:100.2.223.30:6642

Set NB/SB connection inactivity_probe does not work right.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/825269

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/825269
Committed: https://opendev.org/openstack/neutron/commit/0124dab42304596552eda7370c6ad59ee86e145b
Submitter: "Zuul (22348)"
Branch: master

commit 0124dab42304596552eda7370c6ad59ee86e145b
Author: zhouhenglc <email address hidden>
Date: Wed Jan 19 16:13:12 2022 +0800

    [ovn]Set NB/SB "connection" inactivity probe support multi addresses

    When OVN is clustered, connection be set multiple addresses, inactivity
    probe cannot currently be set correctly. this patch fix it.

    Closes-bug: #1958364

    Change-Id: I5f83d6f47dc60b849cca5830ec3f77c15a446530

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 21.0.0.0rc1 release candidate.