os-net-config-mappings.yaml - Example does not work on most hardware due to "Consistent Network Device Naming"
Bug #1642551 reported by
Harald Jensås
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Harald Jensås |
Bug Description
The following line in OsNetConfigMapp
eth_addr=
On a CentOS or RHEL deployment on baremetal hardware would not have an "eth0" interface. Because of Consisten Netowork Device Naming[1], the interface can be "emX", "enoX" or "pXpX" etc.
tags: | added: newton-backport-potential |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/399040
Review: https:/