I've just started using Foreman to kickstart some CentOS 7 systems on
VMware. I noticed that all of my new CentOS 7 hosts have network devices
with unintuitive names like 'eno16777723' and 'eno33555201'. I was
expecting these interfaces to be name things like 'eno1' & 'eno2'. The new
device names are much more difficult to manage using automation tools.
This strange naming is apparently due to a new RHEL7 feature called
"Consistent Network Device Naming" [1] which doesn't play well with how
VMware numbers it's device numbers?
Apparently this can be disabled by appending the following flags to the
kernel parameters (Per [2])
net.ifnames=0 biosdevname=0
I'm a little unclear how I would append these flags to hosts which are
provisioned using Foreman. I imagine I could either apply them to the
"Kickstart default PXELinux" template in one of the 'append' lines, or
perhaps to the "Kickstart default" template
Has anyone else run into this problem, and how did you solve it?
I wanted to keep the device names as ethXX, so we also explicitly don't
install/allow the biosdevname package.
-salman
···
On Fri, May 27, 2016 at 9:36 PM, Stefan Lasiewski wrote:
I’ve just started using Foreman to kickstart some CentOS 7 systems on
VMware. I noticed that all of my new CentOS 7 hosts have network devices
with unintuitive names like ‘eno16777723’ and ‘eno33555201’. I was
expecting these interfaces to be name things like ‘eno1’ & ‘eno2’. The new
device names are much more difficult to manage using automation tools.
This strange naming is apparently due to a new RHEL7 feature called
"Consistent Network Device Naming" [1] which doesn’t play well with how
VMware numbers it’s device numbers?
Apparently this can be disabled by appending the following flags to the
kernel parameters (Per [2])
net.ifnames=0 biosdevname=0
I’m a little unclear how I would append these flags to hosts which are
provisioned using Foreman. I imagine I could either apply them to the
"Kickstart default PXELinux" template in one of the ‘append’ lines, or
perhaps to the “Kickstart default” template
Has anyone else run into this problem, and how did you solve it?
Quick note, I believe that the option is biosdevname=0 (singular) and not biosdevnames=0 (Plural, with an s). Not sure what actually occurs if biosdevnames is used.
-= Stefan
···
On Fri, May 27, 2016 at 7:29 PM, Salman wrote:
I have this in my PXELinux template under Provisioning Templates, as such:
I wanted to keep the device names as ethXX, so we also explicitly don’t
install/allow the biosdevname package.
-salman
On Fri, May 27, 2016 at 9:36 PM, Stefan Lasiewski slasiewski@lbl.gov > wrote:
I’ve just started using Foreman to kickstart some CentOS 7 systems on
VMware. I noticed that all of my new CentOS 7 hosts have network devices
with unintuitive names like ‘eno16777723’ and ‘eno33555201’. I was
expecting these interfaces to be name things like ‘eno1’ & ‘eno2’. The new
device names are much more difficult to manage using automation tools.
This strange naming is apparently due to a new RHEL7 feature called
“Consistent Network Device Naming” [1] which doesn’t play well with how
VMware numbers it’s device numbers?
Apparently this can be disabled by appending the following flags to the
kernel parameters (Per [2])
net.ifnames=0 biosdevname=0
I’m a little unclear how I would append these flags to hosts which are
provisioned using Foreman. I imagine I could either apply them to the
“Kickstart default PXELinux” template in one of the ‘append’ lines, or
perhaps to the “Kickstart default” template
Has anyone else run into this problem, and how did you solve it?
