diff options
| author |   Guillermo Herrero <guillermo.herrero@enea.com> | 2018-02-02 15:43:56 +0100 |
|---|---|---|
| committer |   Alexandru Avadanii <Alexandru.Avadanii@enea.com> | 2018-02-17 03:03:21 +0100 |
| commit | 7a464cc994463231bb7d5dfbc9a29bcfcea5bbdb (patch) | |
| tree | 31b8cde10575a2e7981e31443dfea607c24ba34e /deploy/scenario/no-ha_odl-l2_bgpvpn_scenario_0.0.1.yaml | |
| parent | 380b7375c8be9f05277c6f991ba70801985ca8fa (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>
(cherry picked from commit 378b4a72c27c941d5e37216edb23f224fbb58e26)
Diffstat (limited to 'deploy/scenario/no-ha_odl-l2_bgpvpn_scenario_0.0.1.yaml')
0 files changed, 0 insertions, 0 deletions