Description of problem: The default parameters of OVN are not suitable for scaling scenarios. Steps to Reproduce: 1. Configure ovn using ovirt-engine-setup Actual results: The parameters are not configure to be suitable suitable for scaling scenarios. Expected results: The parameters are configure to be suitable suitable for scaling scenarios. Additional info: The relevant parameters are - inactivity_probe on ovn-central should be 60000 - external_ids:ovn-remote-probe-interval on ovn-controller should be 60000 - external_ids:ovn-openflow-probe-interval on ovn-controller should be 60
Hints for verification: on Engine machine, ovn-sbctl get connection . inactivity_probe should return 60000 on hosts: ovs-vsctl get open . external_ids:ovn-remote-probe-interval -> 60000 ovs-vsctl get open . external_ids:ovn-openflow-probe-interval -> 60
Fixed in ovirt-engine-ovirt-engine-4.4.3.5 and ovirt-provider-ovn-1.2.32-1.
Verified on - rhvm-4.4.3.5-0.5.el8ev.noarch with: ovirt-provider-ovn-1.2.32-1.el8ev.noarch ovirt-provider-ovn-driver-1.2.32-1.el8ev.noarch Engine: ovn-sbctl get connection . inactivity_probe 60000 Host(the modified script is currently only triggered during host install via ansible): ovs-vsctl get open . external_ids:ovn-remote-probe-interval "60000" ovs-vsctl get open . external_ids:ovn-openflow-probe-interval "60" Note: The OVN tasks are not triggered during re-install flow. They are only triggered on install flow. Will open a bug to handle the re-install flow, as the OVN tasks should be triggered as well when performing host re-install. See BZ 1885132
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 (RHV Engine and Host Common Packages 4.4.z [ovirt-4.4.3]), 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-2020:5212