Network service is failing and not started when interface is binded with dpdk driver and config file is still available.
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-01-19 02:02:39 EST; 44s ago
Docs: man:systemd-sysv-generator(8)
Process: 11031 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
Process: 11247 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: Bringing up interface ens9: Connection successfully activated (D-Bus active path: /org/fr...ction/4)
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: [ OK ]
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: Bringing up interface ens90: Error: Connection activation failed: No suitable device foun...nection.
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: [FAILED]
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: Bringing up interface eth0: Connection successfully activated (D-Bus active path: /org/fr...ction/5)
Jan 19 02:02:39 pupetcentos.redhat.local network[11247]: [ OK ]
Jan 19 02:02:39 pupetcentos.redhat.local systemd[1]: network.service: control process exited, code=exited status=1
Jan 19 02:02:39 pupetcentos.redhat.local systemd[1]: Failed to start LSB: Bring up/down networking.
Jan 19 02:02:39 pupetcentos.redhat.local systemd[1]: Unit network.service entered failed state.
Jan 19 02:02:39 pupetcentos.redhat.local systemd[1]: network.service failed.
This issue was fixed in the openstack/ os-net- config 7.0.0.0b1 development milestone.