이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. Upgrading Satellite or Capsule to Red Hat Enterprise Linux 8 In-Place Using Leapp
Use this procedure to upgrade your Satellite or Capsule installation from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8.
Prerequisites
- Satellite 6.11 or Capsule 6.11 running on Red Hat Enterprise Linux 7.
- Review Known Issues before you begin an upgrade. For more information, see Known Issues in Red Hat Satellite 6.11.
-
If you previously upgraded Satellite or Capsule from an earlier version, and the
/var/lib/pgsqlcontained the PostgreSQL database content before the migration from PostgreSQL 9 to PostgreSQL 12 from the SCL, empty/var/lib/pgsqlbefore proceeding. -
During the upgrade, the PostgreSQL data is moved from
/var/opt/rh/rh-postgresql12/lib/pgsql/data/to/var/lib/pgsql/data/. If these two paths reside on the same partition, no further action is required. If they reside on different partitions, ensure that there is enough space for the data to be copied over. You can move the PostgreSQL data on your own and the upgrade will skip this step if/var/opt/rh/rh-postgresql12/lib/pgsql/data/does not exist.
Prerequisites for Disconnected Environment
If you run Satellite in a disconnected environment, ensure it also meets the following prerequisites:
- You must obtain and deploy Leapp metadata manually. For more information, see Leapp utility metadata in-place upgrades of RHEL for disconnected upgrades.
- You require access to Red Hat Enterprise Linux and Satellite packages. Obtain the ISO files for Red Hat Enterprise Linux 8 and Satellite. For more information, see Section 3.1.2, “Upgrading a Disconnected Satellite Server”.
- For more information on customizing the Leapp upgrade for your environment, see Customizing your Red Hat Enterprise Linux in-place upgrade.
- Since Leapp completes part of the upgrade in a container that has no access to additional ISO mounts, the repositories cannot be served from a locally mounted ISO but must be delivered over the network from a different machine.
- For more information, see How to in-place upgrade an offline / disconnected RHEL 7 machine to RHEL 8 with Leapp?
- Satellite supports DEFAULT and FIPS crypto-policies. The FUTURE crypto-policy is not supported for Satellite and Capsule installations.
- In-place upgrade of Red Hat Enterprise Linux systems in FIPS mode is not supported by Red Hat. Turning FIPS off, upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8, and then turning FIPS on is not supported either. Instead, migrate your Satellite 6.11 to a freshly installed Red Hat Enterprise Linux 8 system with FIPS mode enabled. For more information, see Chapter 5, Migrating Satellite to a New Red Hat Enterprise Linux System.
Procedure
Configure the repositories to obtain Leapp.
On Red Hat Enterprise Linux, enable the
rhel-7-server-extras-rpmsrepository:subscription-manager repos --enable=rhel-7-server-extras-rpms
# subscription-manager repos --enable=rhel-7-server-extras-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Install required packages:
satellite-maintain packages install leapp leapp-repository
# satellite-maintain packages install leapp leapp-repositoryCopy to Clipboard Copied! Toggle word wrap Toggle overflow - For Leapp to perform the upgrade in a disconnected environment, download the metadata and manually extract, as described in Leapp utility metadata in-place upgrades of RHEL for disconnected upgrades.
Set up the following repositories to perform the upgrade in a disconnected environment:
/etc/yum.repos.d/rhel8.repo:Copy to Clipboard Copied! Toggle word wrap Toggle overflow /etc/yum.repos.d/satellite.repo:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Configure Leapp to keep Tomcat packages to ensure the upgrade does not fail:
echo tomcat >> /etc/leapp/transaction/to_keep echo tomcat-lib >> /etc/leapp/transaction/to_keep
# echo tomcat >> /etc/leapp/transaction/to_keep # echo tomcat-lib >> /etc/leapp/transaction/to_keepCopy to Clipboard Copied! Toggle word wrap Toggle overflow Let Leapp analyze your system:
leapp preupgrade
# leapp preupgradeCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you run Satellite in a disconnected environment, add the
--no-rhsmand--enablerepoparameters:Copy to Clipboard Copied! Toggle word wrap Toggle overflow The first run is expected to fail but report issues and inhibit the upgrade. Examine the report in the
/var/log/leapp/leapp-report.txtfile, answer all questions (usingleapp answer), and manually resolve the other reported problems.The following commands show the most common steps required:
rmmod pata_acpi echo PermitRootLogin yes | tee -a /etc/ssh/sshd_config leapp answer --section remove_pam_pkcs11_module_check.confirm=True
# rmmod pata_acpi # echo PermitRootLogin yes | tee -a /etc/ssh/sshd_config # leapp answer --section remove_pam_pkcs11_module_check.confirm=TrueCopy to Clipboard Copied! Toggle word wrap Toggle overflow If
leapp preupgradeinhibits the upgrade with Unsupported network configuration because there are multiple legacy named network interfaces, follow the instructions shown by Leapp to rename the interfaces, followed by an installer run to reconfigure Satellite or Capsule to use the new interface names:satellite-installer --help |grep 'interface.*eth' --foreman-proxy-dhcp-interface DHCP listen interface (current: "eth0") --foreman-proxy-dns-interface DNS interface (current: "eth0")# satellite-installer --help |grep 'interface.*eth' --foreman-proxy-dhcp-interface DHCP listen interface (current: "eth0") --foreman-proxy-dns-interface DNS interface (current: "eth0")Copy to Clipboard Copied! Toggle word wrap Toggle overflow If
eth0was renamed toem0, call the installer to use the new interface name with:satellite-installer --foreman-proxy-dhcp-interface=em0 --foreman-proxy-dns-interface=em0
# satellite-installer --foreman-proxy-dhcp-interface=em0 --foreman-proxy-dns-interface=em0Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Ensure
leapp preupgradehas no issues. Run:
leapp upgrade
# leapp upgradeCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you run Satellite in a disconnected environment, add the
--no-rhsmand--enablerepoparameters:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Reboot the system.
After the system reboots, a live system conducts the upgrade, reboots to fix SELinux labels, then reboots into the final Red Hat Enterprise Linux 8 system.
Leapp finishes the upgrade, watch it with:
journalctl -u leapp_resume -f
# journalctl -u leapp_resume -fCopy to Clipboard Copied! Toggle word wrap Toggle overflow Complete these procedures in Upgrading from RHEL 7 to RHEL 8:
Unlock packages:
satellite-maintain packages unlock
# satellite-maintain packages unlockCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Verifying the post-upgrade state of the RHEL 8 system
- Performing post-upgrade tasks
Lock packages:
satellite-maintain packages lock
# satellite-maintain packages lockCopy to Clipboard Copied! Toggle word wrap Toggle overflow
For Satellite only and not Capsule, if you require SELinux to be in enforcing mode, run the following command before changing SELinux to enforcing mode:
dnf reinstall foreman-selinux katello-selinux --disableplugin=foreman-protector
# dnf reinstall foreman-selinux katello-selinux --disableplugin=foreman-protectorCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Complete the steps for changing SELinux to enforcing mode described in Changing SELinux mode to enforcing in the Upgrading from RHEL 7 to RHEL 8 guide.
Unset the
subscription-managerrelease:subscription-manager release --unset
# subscription-manager release --unsetCopy to Clipboard Copied! Toggle word wrap Toggle overflow