Known issues for migration from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 7
This article contains a list of known issues for migrations from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 7. It also provides possible solutions or workarounds to deal with such problems. The article will be extended as new issues arise.
1. Unable to log in using GDM after upgrade
In case you are using GNOME, you might not be able to log in to a graphical environment after the installation due to certain missing packages. However, you can log in by using the terminal. To work around the problem, type one of the following commands:
# yum install @gnome
or
# bash /root/preupgrade/noauto_postupgrade.d/install_rpmlist.sh ~/preupgrade/kickstart/RHRHEL7rpmlist_obsoleted
Note: If this problem occurs with another desktop environment, install the relevant group.
2. Required actions in Anaconda during migration
Certain actions are required by Anaconda during migration unless you modify the generated Kickstart file accordingly. This is an expected behavior.
2.1. Root password is required
This usually happens when you do not set the root password in the Kickstart file. See the Root password section in this Knowledgebase article.
2.2. I have to reboot manually after installation
The reboot line is not specified by default in the Kickstart file because it might result in an endless installation loop, depending on the installation media and method.
However, if you want to enable automatic reboot after installation, add the following line into the Kickstart file before %post section.
reboot
3. Custom SELinux policy is not applied automatically
This is an expected behavior. Custom SELinux policies are not applied automatically because of possible conflicts with new SELinux policies on the Red Hat Enterprise Linux 7 system. Only certain specific policies are applied, for example, non-standard ports for the Apache HTTP server are enabled when found. You must set and review other SELinux policies manually.
