Created attachment 1413337 [details]
journalctl -xe after enabling DPDK

Description of problem:
After enabling DPDK in openvswitch rpm, ovs fails to finish executing ovs-vsctl commands and the openvswitch.service fails to restart/start. Commands to ovs-vsctl will hang needing CTRL+C to stop, however ovsdb is updated.

   To enable DPDK:

ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true

journalctl -xe logs attached.

Version-Release number of selected component (if applicable):
openvswitch-2.9.0-3.el7fdp.ppc64le.rpm

How reproducible:
Only when DPDK is enabled in openvswitch rpm. Otherwise openvswitch works fine.

Steps to Reproduce:
1. Install openvswitch-2.9.0-3.el7fdp.ppc64le.rpm
2. systemctl start openvswitch
3. ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
4. ovs-vsctl add-br br0
Command hangs

4. systemctl restart openvswitch

Actual results:
# ovs-vsctl add-br br0
(after a long time...)
^C2018-03-26T20:42:30Z|00002|fatal_signal|WARN|terminating with signal 2 (Interrupt)

# ovs-vsctl show
    Bridge "br0"
        Port "br0"
            Interface "br0"
                type: internal
    ovs_version: "2.9.0"

Expected results:
# ovs-vsctl add-br br0
# ovs-vsctl show

Additional info:

This error is due to the file permission's of /proc/self/auxv. In DPDK, commit 1e0a17ac4c816fc41f6cf8c1fcd56149d8927263 introduces a different way to verify file permissions, changing the assertion from != 0 to != 1. 

Possible solution: 

Revert patch 1e0a17ac4c816fc41f6cf8c1fcd56149d8927263 from DPDK 17.11

New patch posted could also be a possible solution:
http://dpdk.org/ml/archives/dev/2018-March/093582.html


This is a bug in DPDK which is part of the openvswitch rpm for ppc64le.