anaconda in F34 and Rawhide recently stopped accepting params
without the inst. prefix, so 'rescue' does nothing except print
a warning now. We need to use `inst.rescue`. This has worked for
quite a long time so will be OK at least on all Fedoras and RHEL
8, not sure about RHEL 7.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Signed-off-by: Brian C. Lane <bcl@redhat.com>
The difference between the anaconda-install-{env,img}-deps packages is how
they treat dependencies. The -env package leaves some dependencies as weak to
allow less featureful builds. The -img package hard-requires everything
Anaconda could potentially use and ensures everything works.
For boot.iso, the latter is preferable. Its usage moves some things from the
templates to that package.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
mk-s390-cdboot has stopped working because the kernel outgrew the
hard-coded offset it used when creating cdboot.img. IBM now has a script
in s390utils that can do the same thing so use the upstream script
instead.
This drops mk-s390-cdboot script, switches the s390 templates to use
mk-s390image from s390utils.
It adds @ROOT@ to cdboot.prm, and sets inst.stage2 so that the installer
image will be found when booting the iso.
Resolves: rhbz#1903923
This should be pulled in by libblockdev-mpath, but for some reason it is
not. It may be related to it being changed to a 'Recommends' -- but we
are not yet sure. So make sure it is included until that can be tracked
down.
Include the generic.ins file on the s390 boot iso, so it's directly bootable
on an LPAR. The full iso already had generic.ins included.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
Resolves: rhbz#1844517
Anaconda creates a user for connecting via ssh during the installation
when the sshpw kickstart command is used. The user is created with
"/sbin/nologin" shell when /etc/default/useradd is missing, which
prevents the user from log into the running installation.
Resolves: rhbz#1843609
This new setting for 'find_multipaths' tries to prevent things like
LVM from going ahead and activating LVM on the individual disks/paths
until there is reasonable certainty (via a timeout) that the device
is not a component of a multipath set.
NOTE: 'smart' is supported by device-mapper-multipath v0.7.7 and later.
Resolves: rhbz#1763906
Signed-off-by: Brian C. Lane <bcl@redhat.com>
