This would put things in parity with the debian image as far as networking is concerned. Add the line rm -fr /etc/udev/rules.d/70* either above or below line #90 in the kickstart script.Īnd hopefully that should take care of that.Ĭc Alternatively, I've also considered replacing NetworkManager from the CentOS image with systemd-networkd.While your approaches look valid, I think it's first worth trying to disable the udev rules for CentOS when building the image by: I guess it did hurt something.at least with 7.7. This is irrelevant in CentOS/RHEL 7, but it won’t hurt anything. I may have removed it since the author of the linked post stated: I thought I included something similar (see step #5) for the Kickstart script for CentOS, but I do not see it there. There is an Ansible rule and pre-seed entry for Debian in the image builder. The intent is to disable the udev rules to prevent device renaming. The fact that this is still causing the device to be renamed on CentOS is definitely troubling.Īs an aside, interestingly, this didn't used to happen, so something with netplan must have changed in CentOS 7.7. In CentOS interface name is typically start with en, in our case, we will assign the following network configuration to the enp1s0 interface (see the next section to know what all network devices are present in our environment).
That's why the generated network config doesn't specify a valid name, but rather an ID used to match the MAC address.
How to configure static DNS on CentOS or Fedora. Yet, a solution may be simpler than we think.īoth NetworkManager (RHEL) and SystemD Networking use predictable network interface naming, so I'd rather not explicitly fuss with their names. This tutorial describes how to configure static DNS settings on CentOS or Fedora. Hi of all, wow!, what a phenomenal deep-dive into this problem.