The 'inactivity_probe' parameter in OVN dbs schemas [0][1] represents the maximum number of milliseconds of idle time on connection to client before sending an inactivity probe message. This parameter is never set by Neutron/TripleO and it is important to allow its configuration since it can be crucial at scale or under heavy load to avoid reconnections. Devstack sets it at deployment time [2] so I'm open to mimic this and move the BZ to TripleO if that's a better approach. [0] https://github.com/ovn-org/ovn/blob/95e41218fd7ea9c288c95744e80ba7caa90b30e2/ovn-sb.ovsschema#L275 [1] https://github.com/ovn-org/ovn/blob/95e41218fd7ea9c288c95744e80ba7caa90b30e2/ovn-nb.ovsschema#L456 [2] https://opendev.org/openstack/devstack/src/branch/master/lib/neutron_plugins/ovn_agent#L699
As a side note, I reported this against Neutron because there might be a bug in ovsdb-server that deletes this inactivity_probe value and it would be a good workaround if we'd reset it from Neutron upon a reconnection. However, since Neutron is not the only SB client (eg. ovn-controller and metadata-agent), it feels weird to let Neutron take the responsibility of configuring a system wide parameter. IMO, the best approach would be to let the deployer do it based on a cluster configuration.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0986