ovs-vswitchd should consider lack of DPDK support when enabled fatal
Bug #1912847 reported by
James Troup
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
New
|
Undecided
|
Unassigned | ||
OpenStack Neutron Gateway Charm |
In Progress
|
Undecided
|
Unassigned | ||
OpenStack Neutron Open vSwitch Charm |
In Progress
|
Undecided
|
Unassigned | ||
charm-ovn-chassis |
New
|
Undecided
|
Unassigned | ||
openvswitch (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
If ovs-vswitchd without DPDK support is run on a system which requires it, the following error is logged:
2021-01-
Unfortunately this is not a fatal error and ovs-vswitchd continues on. It would be much easier from a monitoring and operator ease-of-diagnosis perspective, if ovs-vswitchd exited after this error message.
(ovs-vswitchd was running without DPDK support due to LP #1836713)
Related branches
~afreiberger/charm-prometheus-grok-exporter:lp1912847-add-ovs-grok-patterns
Merged
into
charm-prometheus-grok-exporter:master
at
revision d9f54a98ffcd686fd44e12b770d8d98305212462
- Tom Haddon (community): Abstain
- 🤖 prod-jenkaas-bootstack: Approve (continuous-integration)
- BootStack Reviewers: Pending requested
-
Diff: 45 lines (+27/-1)2 files modifiedsrc/files/grok-patterns.yaml (+2/-0)
src/files/metrics-mapping.yaml (+25/-1)
Changed in openvswitch (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
summary: |
- ovs-vswitchd should consider lack of DPDK support fatal + ovs-vswitchd should consider lack of DPDK support when enabled fatal |
To post a comment you must log in.
Here's a reproducer:
juju deploy ubuntu # onto a vm or metal, can't repro with lxd dpdk-devargs= 0000:01: 00.0'
juju ssh ubuntu/0 sudo apt-get install openvswitch-switch -y
juju ssh ubuntu/0 'sudo ovs-vsctl add-br br0; sudo ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk options:
Error output from the add-port command is:
ovs-vsctl: Error detected while setting up 'dpdk-p0': could not open network device dpdk-p0 (Address family not supported by protocol). See ovs-vswitchd log for details. openvswitch" .
ovs-vsctl: The default log directory is "/var/log/
You can then query 'ovs-vsctl show' and see:
Bridge br0
Interface dpdk-p0
type: dpdk
options: {dpdk-devargs= "0000:01: 00.0"}
error: "could not open network device dpdk-p0 (Address family not supported by protocol)"
Interface br0
type: internal
Port dpdk-p0
Port br0
ovs-vsctl -f csv list Interface | grep 'not supported'
provides a response that could also be alerted on as an active configuration issue rather than alerting on presence of the log entry.
$ sudo ovs-vsctl -f csv list Interface |grep 'not supported' 733a-48fd- aeb1-9423c68e35 4e,[],{ },{},[] ,[],[], [],[],[ ],[],[] ,"""could not open network device dpdk-p0 (Address family not supported by protocol) """,{}, [],0,0, [],[],[ ],[],{} ,[],[], [],[],dpdk- p0,-1,[ ],"{dpdk- devargs= ""0000: 01:00.0" "}",{}, {},{},dpdk
556792cf-