Public bug reported: When I create a new VM with an Ubuntu Server Cloud image and using cloud-init, the network is only configured on the first boot. After the machine has been shut-down and powered up again, the network is no longer configured static and instead uses DHCP.
I’m using the, at the time newest, xenial server cloud image (30.08.2017) and use a VM manager called oVirt that uses KVM for virtualization. cloud-init version 0.7.9 Ubuntu 16.04.3 LTS Steps to reproduce: • Download Ubuntu cloud image from https://cloud-images.ubuntu.com/xenial/ • Mount disk to fix bug #1573095 (https://bugs.launchpad.net/cloud-images/+bug/1573095) • Fix bug with instructions from comment https://bugs.launchpad.net/cloud- images/+bug/1573095/comments/15 • Unmount disk image. • Import Image into oVirt. • Create new virtual machine in oVirt. • Assign disk image to virtual machine. • Add cloud init parameters (including static IP conf.) to virtual machine. • Boot virtual machine. • See that networking works and a static IP is configured (ifconfig). • See that the network is configured in /etc/network/interfaces.d/50-cloud-init.cfg • Shutdown (NOT reboot) the virtual machine. • Power On the virtual machine. • See that DHCP service runs for 5min. • After boot see that network is not configured. • See that file /etc/network/interfaces.d/50-cloud-init.cfg lost its configuration. Other possible causes: • The cloud image might be wrongly configured to run cloud-init at every boot (As reboots are not affected and the server listens for cloud-init configuration data after first boot. Also the ssh hostkey is reset every time the machine boots). My current workaround: • I added the following line to my cloud-init runcmd parameters to copy the cloud network file: - "cp /etc/network/interfaces.d/50-cloud-init.cfg /etc/network/interfaces" • I disable cloud-init manually after first boot by adding the following line to my cloud- init runcmd parameters: - [ touch, "/etc/cloud/cloud-init.disabled" ] ** Affects: cloud-images Importance: Undecided Status: New ** Affects: cloud-init Importance: Undecided Status: New ** Tags: network network-configuration ** Attachment added: "cloud-init_second-boot.tar" https://bugs.launchpad.net/bugs/1715095/+attachment/4944594/+files/cloud-init_second-boot.tar ** Also affects: cloud-images Importance: Undecided Status: New -- 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/1715095 Title: network is only configured on first boot Status in cloud-images: New Status in cloud-init: New Bug description: When I create a new VM with an Ubuntu Server Cloud image and using cloud-init, the network is only configured on the first boot. After the machine has been shut-down and powered up again, the network is no longer configured static and instead uses DHCP. I’m using the, at the time newest, xenial server cloud image (30.08.2017) and use a VM manager called oVirt that uses KVM for virtualization. cloud-init version 0.7.9 Ubuntu 16.04.3 LTS Steps to reproduce: • Download Ubuntu cloud image from https://cloud-images.ubuntu.com/xenial/ • Mount disk to fix bug #1573095 (https://bugs.launchpad.net/cloud-images/+bug/1573095) • Fix bug with instructions from comment https://bugs.launchpad.net/cloud- images/+bug/1573095/comments/15 • Unmount disk image. • Import Image into oVirt. • Create new virtual machine in oVirt. • Assign disk image to virtual machine. • Add cloud init parameters (including static IP conf.) to virtual machine. • Boot virtual machine. • See that networking works and a static IP is configured (ifconfig). • See that the network is configured in /etc/network/interfaces.d/50-cloud-init.cfg • Shutdown (NOT reboot) the virtual machine. • Power On the virtual machine. • See that DHCP service runs for 5min. • After boot see that network is not configured. • See that file /etc/network/interfaces.d/50-cloud-init.cfg lost its configuration. Other possible causes: • The cloud image might be wrongly configured to run cloud-init at every boot (As reboots are not affected and the server listens for cloud-init configuration data after first boot. Also the ssh hostkey is reset every time the machine boots). My current workaround: • I added the following line to my cloud-init runcmd parameters to copy the cloud network file: - "cp /etc/network/interfaces.d/50-cloud-init.cfg /etc/network/interfaces" • I disable cloud-init manually after first boot by adding the following line to my cloud- init runcmd parameters: - [ touch, "/etc/cloud/cloud-init.disabled" ] To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1715095/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
