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 fc0a635bc4)
1. Make sure that the ref we sit on exists. This will also work around
a subtle issue which would cause static deltas to not be used (though
https://github.com/ostreedev/ostree/pull/710 will fix that).
2. Make sure we delete the old refs so that the commit eventually gets
cleaned up.
We need to use the kojipkgs url on the builders because they don't
have access to dl.fp.o. After some discussion we have just decided
to use the kojipkgs url everywhere as the dl.fp.o url is just a
redirect anyway.
We want to build images from ostree ref that gets updated "nightly"
but we want consumers of the image to track the two week releases.
This is part of work for ticket: https://pagure.io/releng/issue/6545
* removes the extra ens3 ifcfg that seems to be added
by dracut at some point (cloud base did this in their
ks a year ago in c509863)
* adds net.ifnames=0 to the bootloader line, because
that seems to be necessary to actually disable consistent
device naming
* enables the network service
see https://pagure.io/atomic-wg/issue/174
Due to #1369794 , anaconda cannot currently manipulate sysv
services in F25+. So to work around this, take 'network' out of
the services lines in all kickstarts and instead manipulate
it in the %post section, with chkconfig.
Also remove rsyslog from the Atomic image services line because
it doesn't appear to be included in the OStree tree at present
and so attempting to enable the service breaks Atomic image
compose, see e.g.:
https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log
also correct the name of the ssh service in fedora-arm-base.ks;
it's sshd not ssh.
Dusty Mabe
Jonathan Lebon
Colin Walters
Jason Brooks
Adam Williamson
Peter Robinson
Dennis Gilmore