Created attachment 1450176 [details] meta-data, user-data and network-config files that can be used for reproduction of the issue Description of problem: When attempting to use a Fedora cloud image locally with qemu/kvm and attempting to pass DNS configuration via a `network-config` file with the nocloud source, the current version of cloud-init (v17.1) completely ignores the setting. Version-Release number of selected component (if applicable): Fedora version: 28. Cloud Init Version: 17.1 How reproducible: Consistently. Steps to Reproduce: 1. Download Fedora Cloud image, such as https://download.fedoraproject.org/pub/fedora/linux/releases/28/Cloud/x86_64/images/Fedora-Cloud-Base-28-1.1.x86_64.qcow2 2. Create network-config, user-data and meta-data files, stick them into an iso and mount into a VM started with this image 3. Login via console or ssh, `cat /etc/resolv.conf`; File contains a search domain, but no nameserver entries. ifcfg-eth0 file also does not contain DNS entries. Actual results: # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=none DEFROUTE=yes DEVICE=eth0 GATEWAY=192.168.254.1 IPADDR=192.168.254.2 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet USERCTL=no Expected results: # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=none DEFROUTE=yes DEVICE=eth0 DNS1=8.8.8.8 DNS2=9.9.9.9 GATEWAY=192.168.254.1 IPADDR=192.168.254.2 NETMASK=255.255.255.0 NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet USERCTL=no Additional info: This issue seems to be fixed in later releases of cloud-init, which is confirmed by manually adding https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/ to the image, upgrading cloud-init to $ cloud-init --version /usr/bin/cloud-init 18.2+67.gfc23ccc9-1.fc28 and forcing a re-run of cloud init, with help from @rharper in #cloud-init.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.