I'd like to add that we are seeing the same behavior as of Centos 7.4 and cloud-init 0.7.9-9.el7.centos.2.x86_64 in centos/os and 0.7.9-9.el7.centos.1.x86_64 in centos/updates.
We have a build pipeline that configures /etc/sysconfig/network-scripts/ifcfg-eth0 but in initial boot and any reboot thereafter it ends up being
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=0a:be:79:ba:6e:ec
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
This only started with the new cloud-init versions in centos 7.4.
Our current solution is to set
network:
config: disabled
in /etc/cloud/cloud.cfg which isn't ideal but works.
I'd like to add that we are seeing the same behavior as of Centos 7.4 and cloud-init 0.7.9-9. el7.centos. 2.x86_64 in centos/os and 0.7.9-9. el7.centos. 1.x86_64 in centos/updates.
We have a build pipeline that configures /etc/sysconfig/ network- scripts/ ifcfg-eth0 but in initial boot and any reboot thereafter it ends up being
# Created by cloud-init on instance boot automatically, do not edit. 0a:be:79: ba:6e:ec
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
This only started with the new cloud-init versions in centos 7.4.
Our current solution is to set
network:
config: disabled
in /etc/cloud/ cloud.cfg which isn't ideal but works.