Red Hat SummitChapter 59. Installation and Booting
FIPS mode unsupported when installing from an HTTPS kickstart source
Installation images do not support FIPS mode during installation with an HTTPS kickstart source. As a consequence, it is currently impossible to to install a system with the
fips=1 and inst.ks=https://<location>/ks.cfg options added to the command line. (BZ#1341280)
PXE boot with UEFI and IPv6 displays the GRUB2 shell instead of the operating system selection menu
When the
Pre-Boot Execution Environment (PXE) starts on a client configured with UEFI and IPv6, the boot menu configured in the /boot/grub/grub.cfg file is not displayed. After a timeout, the GRUB2 shell is displayed instead of the configured operating system selection menu. (BZ#1154226)
Specifying a driverdisk partition with non-alphanumeric characters generates an invalid output Kickstart file
When installing Red Hat Enterprise Linux using the
Anaconda installer, you can add a driver disk by including a path to the partition containing the driver disk in the Kickstart file. At present, if you specify the partition by LABEL or CDLABEL which has non-alphanumeric characters in it, for example:
driverdisk "CDLABEL=Fedora 23 x86_64:/path/to/rpm"
the output Kickstart file created during the
Anaconda installation will contain incorrect information. To work around this problem, use only alphanumeric characters when specifying the partition by LABEL or CDLABEL. (BZ#1452770)
The Scientific Computing variant is missing packages required for certain security profiles
When installing the
Red Hat Enterprise Linux for Scientific Computing variant, also known as Compute Node, you can select a security profile similarly to any other variant's installation process. However, since this variant is meant to be minimal, it is missing packages which are required by certain profiles, such as United States Government Configuration Baseline. If you select this profile, the installer displays a warning that some packages are missing.
The warning allows you to continue the installation despite missing packages, which can be used to work around the problem. The installation will complete normally, however, note that if you install the system despite the warning, and then attempt to run a security scan after the installation, the scan will report failing rules due to these missing packages. This behavior is expected. (BZ#1462647)
