From 6553b85eba734be90a4290186e63c3603c2344fc Mon Sep 17 00:00:00 2001
From: Dusty Mabe <dusty@dustymabe.com>
Date: Mar 29 2017 18:44:31 +0000
Subject: zero out resolv.conf during install


Anaconda is writing an /etc/resolv.conf from the install environment.
The system should start out with an empty file, otherwise cloud-init
will try to use this information and may error:
https://bugs.launchpad.net/cloud-init/+bug/1670052

(cherry picked from commit fc0a635bc48a0293c43da01207e9095039198911)

---

diff --git a/fedora-atomic.ks b/fedora-atomic.ks
index fcd1626..e870608 100644
--- a/fedora-atomic.ks
+++ b/fedora-atomic.ks
@@ -143,4 +143,10 @@ echo "Adding Developer Mode GRUB2 menu item."
 # fails due to RHBZ #1369794
 /sbin/chkconfig network off
 
+# Anaconda is writing an /etc/resolv.conf from the install environment.
+# The system should start out with an empty file, otherwise cloud-init
+# will try to use this information and may error:
+# https://bugs.launchpad.net/cloud-init/+bug/1670052
+truncate -s 0 /etc/resolv.conf
+
 %end
diff --git a/fedora-cloud-base.ks b/fedora-cloud-base.ks
index 6cdd70d..626d1a9 100644
--- a/fedora-cloud-base.ks
+++ b/fedora-cloud-base.ks
@@ -278,5 +278,11 @@ rm -f /etc/sysconfig/network-scripts/ifcfg-ens3
 rm -f /etc/machine-id
 touch /etc/machine-id
 
+# Anaconda is writing an /etc/resolv.conf from the install environment.
+# The system should start out with an empty file, otherwise cloud-init
+# will try to use this information and may error:
+# https://bugs.launchpad.net/cloud-init/+bug/1670052
+truncate -s 0 /etc/resolv.conf
+
 %end