** Changed in: maas-images Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1712680
Title: cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS. Status in cloud-init: Fix Released Status in MAAS: Invalid Status in maas-images: Fix Released Bug description: Using MAAS 2.2.2 and newest CentOS image that uses cloud-init cloud- init-0.7.9+224.g681baff-1.el7.centos.noarch, network configuration re- created after reboot (this is *not* with network passthrough). The configuration created was: [centos@withkvm ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=dhcp DEVICE=eth0 HWADDR=52:54:00:03:02:6e NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet USERCTL=no I changed that to do: [centos@withkvm ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=static DEVICE=eth0 HWADDR=52:54:00:03:02:6e NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet USERCTL=no IPADDR=192.168.122.3 NETMASK=255.255.255.0 GATEWAY=192.168.122.2 However, after I reboot, the network config is changed: [centos@withkvm ~]$ sudo cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=dhcp DEVICE=eth0 HWADDR=52:54:00:03:02:6e NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet USERCTL=no Related bugs: * bug 1782315: cloud-init blocks the boot process if it can't reach its MAAS datasource To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1712680/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp