Commit 3dadef5a21 didn't actually work
because it set the value as root. This commit fixes it to set it under
the liveuser instead.
Thanks to adamw for figuring out what's going on!
Test for $LIVE_ROOT (set by livecd-creator) before running commands
specific to a livecd-creator build.
Do not modify the Lorax template during livemedia-creator builds;
the change belongs in Lorax itself.
Related: https://github.com/weldr/lorax/pull/1107
Resolves: rhbz#1430546
Since Fedora 30, license files are missing from the ISO filesystem
of live images (including official builds). The source path to the
license files changed when they were moved into a subpackage named
fedora-release-common (or generic-release-common).
As discussed here:
https://fedoraproject.org/wiki/Changes/RemoveDeviceMapperMultipathFromWorkstationLiveCD
And on the anaconda devel list, we do not want device-mapper-multipath
on the livecd / on installs done from the livecd, because rather then
properly supporting hotplug udev add/change events it brings in
the long obsolete systemd-udev-settle.service which causes significant
delays during boot.
Since multipath is very much a data-center / server only feature we
can simply exclude it from the livecd to get rid of the dependency on
systemd-udev-settle.service .
We also need to exclude fcoe-utils since that depends on
device-mapper-multipath. Since FCOE too is a data-center / server
only feature, we can simply exclude fcoe-utils too.
This is done so that it's easy spot large packages that are not
necessary and identify packages that have grown in size too much
by diffing the image compose logs.
sed "s/rpm -qa/rpm -qa --qf '%{size}\\\\t%{name}-%{version}-%{release}.%{arch}\\\\n' |sort -rn/" -i *.ks
The "auth --useshadow --passalgo=sha512" is long default and auth option
itself has moved to authselect and is obsolete so this actually pulls
in extra dependencies. Drop it as the shadaow and sha512 are defaults.
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
There was race condition between hostname taking effect and lightdm setting up
Xorg service that X client would fail to find a proper xauth entry to connect
the X server.
hostnamectl will also rewrite /etc/hostname.
As livesys and livesys-late are still SysV services, they need
systemd-sysv-install to work, which is part of chkconfig. Until
now chkconfig was getting pulled into live images via packages
that require update-alternatives, which was previously part of
chkconfig - but it just got split into its own package, so now
those packages don't pull in chkconfig any more.
This broke the KDE live image and probably several others in
recent Rawhide, livesys and livesys-late don't run so there's
no 'liveuser' and root isn't accessible. Workstation didn't
break because a java package still pulls chkconfig into it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Recently all Anaconda files required only for the live installation
(the liveinst script, the desktop file and others) have been split into a sub-package
called anaconda-live.
This was done to prevent these files from littering both network
installation images as well as user systems when Anaconda gets pulled
in as a dependency during a package installation transaction.
At the moment anaconda-live is stilled pulled in as a direct dependency
of the anaconda-gui sub package, but once this commit has been merged
into the Fedora kickstart repository, we can drop this temporary
dependency, removing the package from non-live installations.
It was removed from the @core group in fedora-comps d7faeb5,
but we are still using stone-age sysv-style scripts for the
early boot live image setup stuff (livesys and livesys-late),
so we need it installed in live images. Without this, lives are
utterly broken, because livesys fails almost immediately and
does not do any of the expected live customizations.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
For livemedia-creator builds, inject install code into the lorax
template live/x86.tmpl that copies the script livecd-iso-to-disk
into the .iso filesystem at /LiveOS when livecd-tools is present in
the install image. This fixes commit 18d30b3, which failed in this.
Use the anaconda-install-env-deps metapackage to pull in the
Anaconda dependencies needed in the installation environment.
The anaconda-install-env-deps metapackage lists all install time
dependencies and makes it possible for packages such as
Initial Setup to depend on Anaconda without pulling all
the (mainly storage related) install time dependencies
to the installed system.
The same is applicable for dirinstall which also does
not require the install time dependencies as it is just
installing to a local folder.
This also fixes rhbz#1561047 as anaconda-install-env-deps
package has a Requires on udisks2-iscsi.
Grabbing coredumps on live systems is not a good idea. Either there is
no persistent storage, or it will be really slow and also small. So
disable abrtd and stop it in the same way as other services.
The arch-specific sub-packages that provide grub2-efi on each
arch are listed in @anaconda-tools comps group anyway (so this
is redundant), and requiring it by name in a kickstart causes
i686 live image composes to fail because it is no longer built
for i686.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
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.
