[Bug 1899369] [NEW] ovn-controller: Disable ofctrl probe by default

Frode Nordahl 1899369 at bugs.launchpad.net
Sun Oct 11 19:06:39 UTC 2020


Public bug reported:

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.

Symptoms of this problem is that a OVN controller is either unable to do
initial programming of a switch for a host with many ports and flows or
that updates are lost on a functional system. The following will be
printed in the log:

2020-10-11T18:56:09.355Z|30186|rconn|ERR|unix:/var/run/openvswitch/br-
int.mgmt: no response to inactivity probe after 5 seconds, disconnecting

0: https://github.com/ovn-org/ovn/commit/c99069c8934c9ea55d310a8b6d48fb66aa477589
1: https://github.com/ovn-org/ovn/commit/b8af8549396e62d6523be18e104352e334825783

** Affects: ovn (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  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.
  
+ Symptoms of this problem is that a OVN controller is either unable to do
+ initial programming of a switch for a host with many ports and flows or
+ that updates are lost on a functional system. The following will be
+ printed in the log:
+ 
+ 2020-10-11T18:56:09.355Z|30186|rconn|ERR|unix:/var/run/openvswitch/br-
+ int.mgmt: no response to inactivity probe after 5 seconds, disconnecting
+ 
  0: https://github.com/ovn-org/ovn/commit/c99069c8934c9ea55d310a8b6d48fb66aa477589
  1: https://github.com/ovn-org/ovn/commit/b8af8549396e62d6523be18e104352e334825783

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ovn in Ubuntu.
https://bugs.launchpad.net/bugs/1899369

Title:
  ovn-controller: Disable ofctrl probe by default

Status in ovn package in Ubuntu:
  New

Bug description:
  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.

  Symptoms of this problem is that a OVN controller is either unable to
  do initial programming of a switch for a host with many ports and
  flows or that updates are lost on a functional system. The following
  will be printed in the log:

  2020-10-11T18:56:09.355Z|30186|rconn|ERR|unix:/var/run/openvswitch/br-
  int.mgmt: no response to inactivity probe after 5 seconds,
  disconnecting

  0: https://github.com/ovn-org/ovn/commit/c99069c8934c9ea55d310a8b6d48fb66aa477589
  1: https://github.com/ovn-org/ovn/commit/b8af8549396e62d6523be18e104352e334825783

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1899369/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list