A change [0] prior to the release of OVN v20.03.0 introduced a change of behavior where the inactivity probe for the ofctrl connection defaults to 5 seconds. Since this normally is a unix socket the default was not to have a inactivity probe at all.
On a busy system a inactivity probe of 5 seconds is not enough for the OVN Controller to complete programming of the switch.
The change of behavior was corrected in [1] and I think it would be beneficial if Ubuntu backported this fix to the OVN package rather than having charms and/or end users work around the issue by manually configuring the timeout through the `external-ids:ovn-openflow-probe-interval` key in the Open_vSwitch table.
A change [0] prior to the release of OVN v20.03.0 introduced a change of behavior where the inactivity probe for the ofctrl connection defaults to 5 seconds. Since this normally is a unix socket the default was not to have a inactivity probe at all.
On a busy system a inactivity probe of 5 seconds is not enough for the OVN Controller to complete programming of the switch.
The change of behavior was corrected in [1] and I think it would be beneficial if Ubuntu backported this fix to the OVN package rather than having charms and/or end users work around the issue by manually configuring the timeout through the `external- ids:ovn- openflow- probe-interval` key in the Open_vSwitch table.
0: https:/ /github. com/ovn- org/ovn/ commit/ c99069c8934c9ea 55d310a8b6d48fb 66aa477589 /github. com/ovn- org/ovn/ commit/ b8af8549396e62d 6523be18e104352 e334825783
1: https:/