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.
Hi, How to reproduce? Can you provide the versions? OSPd? ovs? Thanks,
(In reply to Eyal Dannon from comment #2) > How to reproduce? > Can you provide the versions? OSPd? ovs? With any OvS version on OSP10, after the DPDK interface is bound to the PMD, restart the network service. It will fail to restart, because the DPDK interface is not visible to the kernel, but ifcfg file is not removed. with this patch, the ifcfg file of the DPDK interface is removed. os-net-config-5.1.0-1.el7ost should have this issue as it has been fixed in the next version.
The network service came up after a reboot, Verified on 2017-05-23.4 puddle, With the following os-net-config package: # rpm -qa | grep os-net-config os-net-config-5.2.0-2.el7ost.noarch Thanks
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/RHBA-2017:1585