diff options
author | Guillermo Herrero <guillermo.herrero@enea.com> | 2018-02-02 15:43:56 +0100 |
---|---|---|
committer | Guillermo Herrero <guillermo.herrero@enea.com> | 2018-02-02 15:43:56 +0100 |
commit | 378b4a72c27c941d5e37216edb23f224fbb58e26 (patch) | |
tree | 8d6e2f8a74d306d9c2dbf93ae499ba470d34f24e /mcp/metadata | |
parent | 252fd2b6fe32a77a4014ce33ead9f77817b1d2c9 (diff) |
[baremetal] Fix: wrong nic name idf index
This was only affecting pod deployments with
different board models, under the current limited
support:
- 3 KVMs will be same model and have the same NIC names
- 2 Compute nodes will be the same model and have same NIC names
For the computes nodes, br-mesh NIC name was wrong due
to incorrect idf mapping
Change-Id: I9685b35cb23b03be9fc0e6fe16c0712a9ad70e19
Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
Diffstat (limited to 'mcp/metadata')
0 files changed, 0 insertions, 0 deletions