Error on ovnkube-node pods: "assertion ovs_list_is_empty(&f->list_node) failed in flood_remove_flows_for_sb_uuid()"

Solution Verified - Updated -

Issue

  • OVN controller does not get ready on ovnkube-node pods, throwing errors like the following one:
2021-03-29T14:15:24.918797367Z 2021-03-29T14:15:24Z|00002|rconn(ovn_pinctrl0)|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting...
2021-03-29T14:15:24.920258767Z 2021-03-29T14:15:24Z|00003|rconn(ovn_pinctrl0)|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected
2021-03-29T14:17:47.892178610Z ovn-controller: 2021-03-29T14:17:47.892264515Z controller/ofctrl.c:1198: assertion ovs_list_is_empty(&f->list_node) failed in flood_remove_flows_for_sb_uuid()2021-03-29T14:17:47.892291742Z
  • The problem implies that the ovnkube-node pods are being constantly restarted.

Environment

  • Red Hat OpenShift Container Platform 4.6 and 4.7.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In