bbaassssiiee/fedora-kickstarts
1
0
Fork 0
forked from srbala/fedora-kickstarts
Code Issues Pull Requests Releases Activity

zero out resolv.conf during install

Browse Source 
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
This commit is contained in:
Dusty Mabe 2017-03-28 14:56:51 -04:00
parent 483ef44d99
commit fc0a635bc4
No known key found for this signature in database
GPG Key ID: 3302DBD73952E671
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
fedora-atomic.ks
View File

@ -131,4 +131,10 @@ echo "Adding Developer Mode GRUB2 menu item."
# fails due to RHBZ #1369794 # fails due to RHBZ #1369794
/sbin/chkconfig network off /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 %end

6
fedora-cloud-base.ks
View File

@ -255,5 +255,11 @@ rm -f /etc/sysconfig/network-scripts/ifcfg-ens3
rm -f /etc/machine-id rm -f /etc/machine-id
touch /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 %end