When performing the kickstart upgrade with a key for advanced platforms, additional repositories were not enabled, and only the base repository packages were upgraded.
Adding a VT repository to the kickstart file and using the "key --skip" command resulted in an error when trying to install the Virtualization-en-US package.
Reusing the LVM logical volumes from the previous installation process caused the bootloader program to use the old disk labels so that the system was unable to boot.
If the file system label ended with the "0" character, this character was stripped so that the existing file system label was different from what was explicitly specified by the user.
The "CMSCONFFILE" parameter could have contained wrong syntax. This could have resulted in certain Bash errors on IBM S/390.
Specifying the "CMSDASD" parameter with a hex number using uppercase letters resulted in the kickstart file not being found.
The installer environment lacked the symbolic links for stdin, stdout, and stderr. As a result, the console output to the files instead of the screen.
The installer used the maximum LV size limit based on the LVM 1 limits. Now, the maximum LV size limit is based on the LVM 2 limits.
Only stderr was logged to the output file during the kickstart installation. Now, stdout is also logged.
Using the parameter "--no-ssh" in kickstart failed to propagate the same parameter to /root/anaconda-ks.cfg.
The "--no-ssh" parameter was not documented in /usr/share/doc/anaconda-*/kickstart-docs.txt.
Downloading the Red Hat Enterprise Linux Release Notes resulted in errors, even though the Release Notes were downloaded successfully.
The /var/log/ directory required by the Subscription Manager logging was not created.
The list-harddrives script did not work as expected.
Errors emitted by the kickstart scripts were not properly reported to the user.
Even though the installation was run with IPv6 enabled, IPv6 was disabled in the installed environment.
The Solarflare network adapters were not available to the user during the installation.
The installation performed on an XTS-encrypted partition failed.
When specifying the network mask during the manual network setup using the dotted format, a spurious error message was displayed.
When using the bnx2i iSCSI adapters, the installer did not read IP from iBFT properly.
The "dhcptimeout" option was not propagated.
The "--only-use" ignoredisk parameter did not work so that Anaconda terminated unexpectedly.
portmap was not available in rescue mode so that the rescue environment was unable to mount NFS volumes.
Adding "-@conflicts" to the kickstart file did not prevent the conflicting packages from the @conflicts group to be installed if other packages depended on the conflicting packages. Now, the conflicting packages and packages that depend on the conflicting packages are not installed.
- BZ#758106, BZ#768082
Pressing Esc in certain Anaconda windows had the same result as clicking "OK". With this update, pressing Esc has the same result as clicking "Cancel".
The Network Configuration interface localization was incomplete.
The Installation Number screen did not display links under the pa_IN locale.