[DPDK] OVS-agent doesn't start after stop and start compute
Bug #1671804 reported by
Kristina Berezovskaia
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Committed
|
High
|
Ivan Udovichenko |
Bug Description
After stop and start compute with DPDK ovs agent on this node doesn't start
Steps:
1) Deploy bare-metal env with DPDK
2) Stop compute
3) Start compute
Expected result: computer starts with all services
Current result: ovs-agent doesn't start
Workaround:
restart ovs-agent manually
Iso: ISO_ID=1411
VLAN, 3 controllers + 2 compute-cinder with DPDK
Diagnostic snap:
https:/
Changed in mos: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → MOS Linux (mos-linux) |
tags: | added: area-linux |
To post a comment you must log in.
Ivan, could you take a look please? openvswitch- agent's systemd unit hasn't openvswitch-switch dependency in the 'After' section.
Seems like neutron-
Perhaps, script which generates unit from sysv init script doing it in the wrong way.