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 protected]> 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 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1958364 Title: [ovn]Set NB/SB connection inactivity_probe does not work for cluster Status in neutron: Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1958364/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
