Network Service is failing with DPDK

Bug #1657661 reported by Jaganathan Palanisamy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

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.

Tags: networking
Changed in tripleo:
assignee: nobody → Jaganathan Palanisamy (jaganathanp)
tags: added: networking
Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → pike-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-net-config 7.0.0.0b1

This issue was fixed in the openstack/os-net-config 7.0.0.0b1 development milestone.

Changed in tripleo:
milestone: pike-1 → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-net-config 5.2.0

This issue was fixed in the openstack/os-net-config 5.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-net-config 6.1.0

This issue was fixed in the openstack/os-net-config 6.1.0 release.

Changed in tripleo:
milestone: pike-2 → pike-3
Revision history for this message
Emilien Macchi (emilienm) wrote :

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

Changed in tripleo:
assignee: Jaganathan Palanisamy (jaganathanp) → nobody
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.