This change is to fix the finding DPDK device name issue in
OvS DPDK derive parameters logic. Currently mistral fails to
derive OvS DPDK parameters in NIC Partitioning and getting
error 'Unable to determine NUMA node for DPDK NIC:'
Change-Id: I8dfc2494d35d5fce52d573f9edcafbe11ab7faac
Closes-Bug: #1855159
(cherry picked from commit 9641cc2ccb9d6bc5757f2bb888b374dedc2d2733)
Reviewed: https:/ /review. opendev. org/698621 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=dd354ee4d6e b05c003de40006c bdb0895099f2c8
Committed: https:/
Submitter: Zuul
Branch: stable/train
commit dd354ee4d6eb05c 003de40006cbdb0 895099f2c8
Author: Jaganathan Palanisamy <email address hidden>
Date: Wed Dec 4 23:54:39 2019 +0530
OvS DPDK parameters failing in NIC Partitioning
This change is to fix the finding DPDK device name issue in
OvS DPDK derive parameters logic. Currently mistral fails to
derive OvS DPDK parameters in NIC Partitioning and getting
error 'Unable to determine NUMA node for DPDK NIC:'
Change-Id: I8dfc2494d35d5f ce52d573f9edcaf be11ab7faac 5757f2bb888b374 dedc2d2733)
Closes-Bug: #1855159
(cherry picked from commit 9641cc2ccb9d6bc