for rhbz#1392468 I was told that what we had should never have worked.
A bug in anaconda was fixed causing the need for the user or root
spokes to have to be dealt with. locking the root account should
satisfy everything.
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
This prevents systemd to update it during boot if DHCP supplies a
hostname, which causes sddm to not start. See
https://bugzilla.redhat.com/show_bug.cgi?id=1370222
Signed-off-by: Kamil Páral <kparal@redhat.com>
So is seems that if you remove the machine-id file it won't regenerate the file
but if you touch the file and leave it empty on boot it'll put a new machine-id
in the empty file. So work around this bug ("feature"?) by touching the file
so we don't have other issues in the process.
We're track the outcome of this in RHBZ 1379800
As referenced on the arm list [1] and as already being done on the docker image we
should remove the unique /etc/machine-id file on compose artifacts to ensure it's
regenerated and unique on each deployed host/device. This unifies the process across
all base ks so it's inherited for each artifact.
[1] https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/Q3YZVF5P2OLLPUJQ2LYZSTKWGGDIU6QO/
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
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.
We need to have chronyd start after livesys has finished so that
the config for chronyd gets rewritten before it starts. If not it
will overwrite the system clock with a time that will be incorrect
(US eastern stored as local time instead of UTC) for most people.
This fixes bug 1018162.
Per discussion on #1169979, fontconfig upstream think they have
the bugs licked, so this shouldn't be needed any more. We need
to check the nightly lives after this and see if their caches
are now correct.
As livecd-creator is still yum based, we only get yum's yumdb during
live image composes. To work this around, this commit adds a %post
script to fedora-live-base.ks to migrate yum's yumdb over to dnf.
https://bugzilla.redhat.com/show_bug.cgi?id=1274319
The ModemManager package is already installed for all live images;
it should be enabled so users can connect to WWAN right after boot
using the NetworkManager applet.
Signed-off-by: David Ward <david.ward@ll.mit.edu>
This is pretty cosmetic as live and cloud images don't use passwords
and they install with sha512 fine, but some people may use these
kickstarts as a base for their spins, so we should use best practices.
Add fedora-release-nonproduct to fedora-live-base.ks to ensure it gets
pulled in for all spins. In order to avoid it getting pulled in to
the Workstation product that is also based on fedora-live-base.ks,
explicitly exclude fedora-release-nonproduct in workstation kickstart
file.
https://bugzilla.redhat.com/show_bug.cgi?id=1154235
The gnome-settings-daemon updates plugin is gone and update downloading
is handled by gnome-software instead. Adapt the live image schema
overrides for the changes.
Do not hardcode the fedora-release package name in the %post scriptlet
(in the place that imports the Fedora RPM GPG key). Instead, use
"--whatprovides system-release", which is strictly equivalent if
fedora-release is used, but also works when the *-release package is
named differently.
This makes live easier for remixes, which have to replace fedora-release
with generic-release or ${remixname}-release. They would otherwise have
to edit fedora-live-base.ks.
Now the switch between using the rawhide repo and the normal repos
can be done by just switching comment lines in one place
(fedora-repo.ks). (Note that the repo lines in fedora-install.ks
don't get changed for branching.)
Using >> means we have a custom.conf file that looks like this:
[daemon]
...
[daemon]
AutomaticLoginEnable=True
AutomaticLogin=liveuser
Which is the first reason why it's failing. Change the cat append to replace as
the other sections are optional.
Additionally, the livesys legacy service is not completing before gdm is being
started, which means the config file is being read before it has been altered.
This can be fixed by adding a LSB-style "X-Start-Before: display-manager" in the
header of livesys.
