- Due to a bug in the multipath output parsing code, when installing Red Hat Enterprise Linux 6 on an IBM Power system with JBOD (Joined Body Of Disks — more than one hard drive attached to the same SAS controller), Anaconda could detect these multiple hard drives as a multipath device. This in turn caused the partitioning of the hard drive to fail, causing the installation of the system to fail as well. This update fixes the parsing code and the system is installed correctly.
- The Anaconda installer did not wait for BIOS storage devices to initialize when booted with the
ks:bd:<bios disk>:/ks.cfgcommand-line option. As a consequence, BIOS storage devices could not be found and the installation could fail. To fix this bug, a delay algorithm for BIOS devices has been added to the code path used when booting with
ks:bd:<bios disk>:/ks.cfg. As a result, Anaconda tries to wait for BIOS devices to initialize.
- The file system migration from ext2 to ext3 did not work because Anaconda did not modify the
/etc/fstabfile with the new ext3 file system type. Consequently, after the installation, the file system was mounted as an ext2 file system. With this update, Anaconda properly sets the migrated file system type in
/etc/fstab. Thus, the file system is mounted as expected after installation.
- When installing Red Hat Enterprise Linux 6.4 Beta using the kickstart file, which included the partition scheme, LVM incorrectly removed the dashes from Logical Volume and Volume Group names. This caused the names to be malformed. This update fixes the aforementioned function to correctly format Logical Volume and Volume Group names during the installation process.
- Using IPv6 to install Red Hat Enterprise Linux 6.3 (both Alpha and Beta) on a z/VM guest enabled the user to SSH to the system and proceed with the language selection screen. However, after this step, the installation stopped and the SSH session was closed. With this update, the IPv6 installation on a z/VM guest is successful on Red Hat Enterprise Linux 6.4.
- A kickstart installation on unsupported hardware resulted in a dialog box asking for confirmation before proceeding with the installation process. As a consequence, it was not possible to perform a kickstart installation on unsupported hardware without any user input. To fix this bug, a new
unsupported_hardwarekickstart command has been added, which skips the interactive dialog warning when installing a system on unsupported hardware without user input.
- When a
/bootpartition was on a RAID device, inconsistent messages were returned because it was not supported to have this partition on such a device. These varied messages were confusing. To fix this bug, the error messages have been corrected to make sense and to not duplicate each other.
- Kernel modules containing Microsoft paravirtualized drivers were missing in the installation environment. To fix this bug, kernel modules with Microsoft PV have been added to the installation environment. As a result, better support for Microsoft virtualization is provided.
- Modules with VMware PV drivers were not included in the installation environment. This update adds the modules with VMware PV drivers to provide better virtualization support.
udevdevice manager was not used to resolve kickstart
raid --onpartdisk references. As a consequence, the
/dev/disk/by-id/path could not be used properly. With this update, the
udev_resolve_devspec()function is used to resolve the
--onpartcommand option. As a result, the
raid --onpartcommand can now use the
/dev/disk/by-id/paths as expected.
- The Anaconda installer did not use the
udevdevice manager to resolve
/dev/disk/by-id/names. This meant the kickstart installation method did not work with
/dev/disk/by-id/names. To fix this bug, Anaconda is now using
/dev/disk/by-id/names. As a result, kickstart installations using
/dev/disk/by-id/names work as expected.
- When installing a system using the text mode on a machine which already had Red Hat Enterprise Linux installed on it, a traceback error occurred when thebutton was used to go back from any dialog after the time zone dialog. With this update, disks are rescanned when moving back through the upgrade dialog, thus preventing this bug.
- The Anaconda installer called the
modprobetool without the
-bargument that enabled blacklists. Consequently, modules were not blacklisted. To fix this bug, the required argument has been added to modprobe call. As a result, modules are blacklisted as expected.
- The Anaconda installer appended the
boot=parameter on the command line whenever the
fips=1parameter was used. With this update, Anaconda appends the
boot=parameter only when the
fips=1parameter is used and
/bootis on a separate partition.
- This update fixes a typographical error in Korean version of a warning message used to alert users of a root password that is too simple.
- The Anaconda installer did not verify package checksums against the checksum in the repository metadata. A package which did not match the repo metadata checksum could be installed by the Yum utility. As a consequence, an incorrect package could be installed with no errors returned. This update adds verification of the package checksum against the checksum in the repository metadata.
- IPv6 configuration options of the installer's text UI (user interface) were using descriptions suggesting misleading meaning. Consequently, the description could mislead the users with DHCPv6 configured to use Dynamic IPv6 configuration (DHCPv6) which used DHCPv6 exclusively without using SLAAC automatic configuration. To fix this bug, the first option (
Automatic neighbor discovery) has been renamed to
Automatic; it is the (SLAAC) automatic configuration with the option of using a DHCPv6 server based on RA server configuration. The second option (
Dynamic IP configuration (DHCPv6)) was renamed to
Automatic, DHCP only, which describes the actual configuration to be used more accurately. These descriptions are now the same as those used by Network Manager. As a result, it is now clearer that the third option (
Automatic, DHCP only) is using the DHCPv6 server exclusively.
- The command-line interface of the fcoe-utils package in Red Hat Enterprise Linux 6.3 was changed but the installer did not adapt to this change correctly. As a consequence, FCoE initiators were not able to log in to remote storages, which could then not be used for installation. To fix this bug, the
fipvlancommand arguments have been fixed to use the new
-foption correctly. As a result, the installer now logs in to a FCoE remote storage correctly, and can be used for installation purposes.
- Repositories without size data caused a divide-by-zero error. Consequently, the installation failed. With this update, repositories without size data do not cause a divide-by-zero error and the installation succeeds.
- Support for the
--hibernationoption was only added to the
--hibernationdid not work with the
logvolcommand. To fix this bug, support for
--hibernationhas been added to the
logvolcommand. As a result,
--hibernationnow works with the
linksleepoption used to be applied only for the
ksdevice=boot parameter using the value link. Consequently, when the
ksdeviceboot parameter was supplied a value containing a device name or a MAC address, the
linksleepboot parameter did not take effect. Without waiting for the link, as required by the
linksleepboot parameter, the installer could fail. To fix this bug, the
linksleepboot parameter has been added to code paths where the to-be-activated device is specified. As a result, the
linksleepboot parameter is honored also for installation where the
ksdeviceboot parameter is supplied a value containing a device name or a MAC address.
- The Anaconda installer did not check lengths of Logical Volume Manager (LVM) Volume Group names or Logical Volume names. As a consequence, an error occurred when creating disk partitions. To fix this bug, the length of LVM Volume Group names has been truncated to 32 characters and Logical Volume names to 16 characters. As a result, the installation completes successfully.
- Previously, Anaconda failed to enable add-on repositories when upgrading the system. Consequently, packages from the add-on repositories were not upgraded. This update allows Anaconda to enable add-on repositories when the system is upgrading and packages from the add-on repositories are upgraded as expected.
- With this update, the
--vlanid=kickstartoptions can be used to allow users to set a virtual LAN ID (802.1q tag) for a specified network device. By specifying either one of these options, installation of the system can be done over a VLAN.
- This update allows users to select a LUKS encryption type in the kickstart configuration file.
--bondopts kickstartoptions can now be used to configure bonding as a part of the installation process. For more information on how to configure bonding, refer to the following parts of the Red Hat Enterprise Linux 6 Installation Guide: the Kickstart Options section and the Boot Options chapter.
- When using a kickstart file to install Red Hat Enterprise Linux 6.4, with the new
fcoe kickstartoption, users can now specify, which Fibre Channel over Ethernet (FCoE) devices should be activated automatically in addition to those discovered by Enhanced Disk Drive (EDD) services. For more information, refer to the Kickstart Options section in Red Hat Enterprise Linux 6 Installation Guide.
- RPM signatures are now generated using the sha256sum utility instead of the md5sum utility. With this update, the sha256sum command-line utility is included in Anaconda and is available in the shell during the installation process.