Hi, We may have a regression here: upcall_cb failure: ukey installation fails 018-03-16T18:35:30.891Z|00215|rconn|WARN|br-sig<->tcp:127.0.0.1:6633: connection failed (Connection refused) 2018-03-16T18:59:16.019Z|00001|ofproto_dpif_upcall(pmd21)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:04:30.696Z|00002|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:14:34.379Z|00003|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:19:16.830Z|00004|ofproto_dpif_upcall(pmd57)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:34:14.329Z|00005|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:40:54.315Z|00002|ofproto_dpif_upcall(pmd63)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:42:54.311Z|00001|ofproto_dpif_upcall(pmd64)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:47:54.300Z|00003|ofproto_dpif_upcall(pmd63)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T20:54:45.355Z|00005|ofproto_dpif_upcall(pmd57)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:09:50.549Z|00001|ofproto_dpif_upcall(pmd65)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:19:50.533Z|00002|ofproto_dpif_upcall(pmd65)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:24:50.523Z|00003|ofproto_dpif_upcall(pmd65)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:29:50.662Z|00006|ofproto_dpif_upcall(pmd57)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:37:24.204Z|00006|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:44:52.604Z|00002|ofproto_dpif_upcall(pmd54)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T21:59:54.158Z|00008|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T22:04:50.453Z|00005|ofproto_dpif_upcall(pmd65)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T22:09:54.144Z|00009|ofproto_dpif_upcall(pmd66)|WARN|upcall_cb failure: ukey installation fails 2018-03-16T22:15:04.138Z|00005|ofproto_dpif_upcall(pmd63)|WARN|upcall_cb failure: ukey installation fails [root@det1-compute-0 openvswitch]# rpm -qa | grep openvswitch openvswitch-ovn-central-2.6.1-24.git20180130.aconole.el7ost.x86_64 openvswitch-ovn-common-2.6.1-24.git20180130.aconole.el7ost.x86_64 python-openvswitch-2.6.1-24.git20180130.aconole.el7ost.noarch openvswitch-debuginfo-2.6.1-24.git20180130.aconole.el7ost.x86_64 openvswitch-test-2.6.1-24.git20180130.aconole.el7ost.noarch openvswitch-2.6.1-24.git20180130.aconole.el7ost.x86_64 openstack-neutron-openvswitch-9.4.1-1.el7ost.noarch openvswitch-ovn-host-2.6.1-24.git20180130.aconole.el7ost.x86_64 [root@det1-compute-0 openvswitch]#
Clearing the needsinfo on this - the RPM had been provided, and just forgot to clear the flag.
Verified with ovs version openvswitch-2.9.0-19.el7fdp.1.x86_64.
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, 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/RHSA-2018:2102