+++ This bug was initially created as a clone of Bug #1409097 +++
Description of problem:
As a part of OSPD10 SR-IOV deploymnet, I have configured the compute yaml file (please find it attached) to use nic id's (nic1, nic2, nic3, etc).
The deployment got stuck on step 5 and eventually it fails due to a timeout.
I have established a connection to one of the computes, and found out in "/var/log/messages" that the nics order isn't correct as it should, it have been changed after the creation of the VF's. nic4 should be mapped to ens2f0 and nic5 should be mapped to ens2f1 (see attached image).
I have tried to use nic names (ens1f0, ens1f1, ens2f0, etc) instead of nic id's, and in this case the overcloud deployment finished successfully.
Version-Release number of selected component (if applicable):
OSPD10 - 1 controller, two computes with SR-IOV enabled.
Steps to Reproduce:
1. deploy ospd with attached yamls.
deployment fails due to timeout
overcloud deploy should finish successfully
Compute hardware, HPE ProLiant DL380 Gen9 server, HPE Ethernet 10Gb 2-port 560SFP sr-iov nic.
--- Additional comment from Ziv on 2016-12-29 08:01 EST ---
--- Additional comment from Ziv on 2016-12-29 08:04 EST ---
--- Additional comment from Saravanan KR on 2017-01-18 02:25:06 EST ---
Review - https://review.openstack.org/#/c/415682/
I have verified with the new patch - os-net-config-5.1.0-1.el7ost, deployment finished successfully.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.