[DPDK] could not open network device dpdk0 (Cannot allocate memory) error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Incomplete
|
Medium
|
Kristina Berezovskaia |
Bug Description
Detailed bug description:
After boot and delete some vns on env with dpdk, vms become to be in ERROR state
Steps to reproduce:
1) Deploy env with DPDK
2) Create flavor for using Huge pages
nova flavor-create hpgs1 auto 512 1 2
nova flavor-key hpgs1 set hw:mem_
3) Boot vm and delete sevral times
Expected results:
All vms become in ACTIVE state
Actual result:
After some times create-delete vm, all new vms are in ERROR state
We can see:
ovs-vsctl show
48ff216b-
Bridge br-int
fail_mode: secure
Port int-br-prv
Port br-int
Bridge br-prv
Port br-prv
Port "dpdk0"
Port phy-br-prv
ovs_version: "2.4.1"
In nova-compute we can see: "BuildAbortExce
In neutron-all log on compute: "Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', '--columns=type', 'list', 'Interface', 'int-br-floating']. Exception: Exit code: 1; Stdin: ; Stdout: ; Stderr: ovs-vsctl: no row "int-br-floating" in table Interface"
Description of the environment:
neutron+vlan, 1 controller, 1 cinder, 3 computes: 2 with dpdk and 1 without
on computes with dpdk:
Nova CPU pinning 14
DPDK CPU pinning 6
Nova Huge pages SizeCount 2.0 MB - 16000
1.0 GB - 10
DPDK Huge Pages
1024
iso:
cat /etc/fuel_build_id:
495
cat /etc/fuel_
495
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-release-
fuel-misc-
python-
fuel-bootstrap
fuel-migrate-
rubygem-
fuel-mirror-
shotgun-
fuel-openstack
fuel-notify-
nailgun-
python-
fuel-9.
fuel-utils-
fuel-setup-
fuel-provision
fuel-library9.
network-
fuel-agent-
fuel-ui-
fuel-ostf-
fuelmenu-
fuel-nailgun-
Changed in mos: | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-library |
Changed in mos: | |
importance: | High → Medium |
Changed in mos: | |
assignee: | Sergey Matov (smatov) → Kristina Kuznetsova (kkuznetsova) |
After several attempts we were not able to reproduce this issue. /bugzilla. redhat. com/show_ bug.cgi? id=1293495.
However, following behavior is seeing if there is DPDK-based application is running on Guest VM. This out-of-scope fact is described in https:/
Detailed description is mailed to dpdk-users list.
Switching priority to Medium since it's reproducibility is not 100%.