Can't ping SR-IOV VM when 2 SR_IOV enable on different numa nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
In Progress
|
High
|
Alexander Adamov |
Bug Description
During verification bug https:/
Steps:
1) Enable sr-iov on 2 interfaces on different numas
2) Deploy env
3) Creat direct port and boot vm
NET_ID_1=$(neutron net-list | grep net_EW_1 | awk '{print$2}')
neutron port-create $NET_ID_1 --binding:vnic-type direct --device_owner nova-compute --name sriov_1
port_id = $(neutron port-list | grep ‘sriov_1' | awk '{print$2}')
nova boot vm1 --flavor m1.small --image ubuntu_image --availability-zone nova:$NODE_1 --nic port-id=$port_id --key-nae vm_key
4)ping vm rom dhcp-interface
Expected results:
Vm is in active state and is pinging
Actual result:
vm is in Active state but isn't pinging
Env:
snap 822? 1 compute with sr-iovs on 1 nume, 1 compute with 2 sr-iovs on different numas
Changed in mos: | |
milestone: | none → 9.2-mu-1 |
importance: | Undecided → Medium |
Changed in mos: | |
importance: | Medium → High |
assignee: | nobody → MOS Neutron (mos-neutron) |
status: | New → Confirmed |
tags: | added: area-neutron neutron |
tags: | added: release-notes |
tags: |
added: release-notes-done removed: release-notes |
Changed in mos: | |
assignee: | Fuel Documentation Team (fuel-docs) → Alexander Adamov (aadamov) |
fuel snapshot: /drive. google. com/open? id=0B05EZCZN- hilaVlxZmxoLXZE ems
https:/