DPDK erros after stop and start compute with DPDK
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Mikhail Zhnichkov | ||
Mitaka |
Fix Released
|
High
|
Mikhail Zhnichkov | ||
Newton |
Fix Committed
|
High
|
Mikhail Zhnichkov | ||
Ocata |
Fix Committed
|
High
|
Mikhail Zhnichkov |
Bug Description
After stop and start compute node vms connectivity stopped for vms on this computer with errors in ovs logs
The same error I can find here^ https:/
Steps to reproduce:
1) DPDK vxlan env
2) Create 1 vm on the first compute (flavor with hp)
3) Create 1 vm on another compute (flavor with hp)
4) Stop 1st compute
5) Wait some time
6) Start compute
7) Try ping vm on this compute
Expected results: ping is available
Actual result: ping is unavailable
8) Boot new vm on the same compute
9) Try ping new vm on this compute
Expected results: ping is available
Actual result: ping is unavailable
In ovs log on compute we have error:
ERROR neutron.
Huge pages after deleting all vms shows that no hp are allocated for DPDK
node-4.
1048576: {'free': 0, 'total': 0},
2048: {'free': 18000, 'total': 19024}
node-3.
1048576: {'free': 0, 'total': 0},
2048: {'free': 19024, 'total': 19024}
Description of the environment:
SNAPSHOT_ID='#688
3 controllers, 2 computes+ceph (18000 2M HP, 1024 for DPDK)
tags: | added: area-python |
Changed in mos: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
status: | New → Confirmed |
Changed in mos: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Vladimir Eremin (yottatsa) |
no longer affects: | mos |
tags: | added: on-verification |
It seems that pinning some CPUs for DPDK is required, otherwise OVS+DPDK will not start after successful deployment.
This case is not validated in nailgun, so currently ovs+dpdk without pinned cpus is an acceptable configuration.