[Bug 1551601] [NEW] DPDK init scripts need some hardening against broken specifications in /etc/dpdk/interfaces

[ChristianEhrhardt]

Public bug reported:

While testing it became obvious, that while working we need some more
resiliency and user friendly messages in case something goes wrong.

Today we have cases like:
- forgot the bus spec -> just doesn't do anything (silently)
- wrong pci ID -> fail to start the service in general
- no module specified -> fail with unclear modprobe error (due to empty name)

The init script needs some hardening and better error messages.

** Affects: dpdk (Ubuntu)
     Importance: High
     Assignee: ChristianEhrhardt (paelzer)
         Status: Triaged

** Changed in: dpdk (Ubuntu)
       Status: New => Triaged

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => High

** Changed in: dpdk (Ubuntu)
     Assignee: (unassigned) => ChristianEhrhardt (paelzer)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1551601

Title:
  DPDK init scripts need some hardening against broken specifications in
  /etc/dpdk/interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1551601/+subscriptions