(In reply to Markos Chandras from comment #10) > Issue reported upstream since OvS seems to be using an internal symbol. > > https://mail.openvswitch.org/pipermail/ovs-dev/2018-May/347430.html > > However, give this is a backport, it's very strange that it made it all the > way to stable branches if this symbol is truly private. I feel that what has happened is this: * during OvS development, the OvS was built/linked against master-branch of DPDK; * for the actual release, OvS is advertised to be built/linked against DPDK x.y (18.02) version which is not exporting/exposing that symbol hence the issue.