Risk Factor: high Title: Packages from unknown repositories may not be installed Summary: 2 packages may not be installed or upgraded due to repositories unknown to leapp: - cockpit-ws (repoid: rhel9-BaseOS) - cockpit-ws-selinux (repoid: rhel9-BaseOS) Remediation: [hint] In case the listed repositories are mirrors of official repositories for RHEL (provided by Red Hat on CDN) and their repositories IDs has been customized, you can change the configuration to use the official IDs instead of fixing the problem. You can also review the projected DNF upgrade transaction result in the logs to see what is going to happen, as this does not necessarily mean that the listed packages will not be upgraded. You can also install any missing packages after the in-place upgrade manually. Key: 9a2b05abf8f45fd7915e52542887bb334bb218ea ---------------------------------------- Risk Factor: high Title: GRUB2 core will be automatically updated during the upgrade Summary: On legacy (BIOS) systems, GRUB2 core (located in the gap between the MBR and the first partition) cannot be updated during the rpm transaction and Leapp has to initiate the update running "grub2-install" after the transaction. No action is needed before the upgrade. After the upgrade, it is recommended to check the GRUB configuration. Key: ac7030e05d2ee248d34f08a9fa040b352bc410a3 ---------------------------------------- Risk Factor: high Title: Leapp detected loaded kernel drivers which are no longer maintained in RHEL 10. Summary: The following RHEL 9 device drivers are no longer maintained RHEL 10: - ip_set Key: fbb11ae5828d624c4e4c91e73d766c8e27b066d9 ---------------------------------------- Risk Factor: high Title: Upgrade is unsupported Summary: Environment variable LEAPP_UNSUPPORTED has been detected. A successful and safe upgrade process cannot be guaranteed. From now on you are continuing at your own risk. Key: 9e5088e3c1f371e020ec777c3d86578f4be143cf ---------------------------------------- Risk Factor: high Title: Detected third-party Python modules for the target Python version Summary: Third-party target Python modules may interfere with the upgrade process or cause unexpected behavior after the upgrade. Non-distribution RPM packages detected: - python3.12-pyyaml Non-distribution modules detected (list possibly incomplete): - /usr/lib64/python3.12/site-packages/_yaml/__init__.py - /usr/lib64/python3.12/site-packages/yaml/__init__.py - /usr/lib64/python3.12/site-packages/yaml/composer.py - /usr/lib64/python3.12/site-packages/yaml/constructor.py - /usr/lib64/python3.12/site-packages/yaml/cyaml.py - /usr/lib64/python3.12/site-packages/yaml/dumper.py - /usr/lib64/python3.12/site-packages/yaml/emitter.py - /usr/lib64/python3.12/site-packages/yaml/error.py - /usr/lib64/python3.12/site-packages/yaml/events.py - /usr/lib64/python3.12/site-packages/yaml/loader.py - /usr/lib64/python3.12/site-packages/yaml/nodes.py - /usr/lib64/python3.12/site-packages/yaml/parser.py - /usr/lib64/python3.12/site-packages/yaml/reader.py - /usr/lib64/python3.12/site-packages/yaml/representer.py - /usr/lib64/python3.12/site-packages/yaml/resolver.py - /usr/lib64/python3.12/site-packages/yaml/scanner.py - /usr/lib64/python3.12/site-packages/yaml/serializer.py - /usr/lib64/python3.12/site-packages/yaml/tokens.py - /usr/lib64/python3.12/site-packages/yaml/_yaml.cpython-312-x86_64-linux-gnu.so - /usr/lib64/python3.12/site-packages/_yaml/__init__.py - /usr/lib64/python3.12/site-packages/yaml/__init__.py - /usr/lib64/python3.12/site-packages/yaml/composer.py - /usr/lib64/python3.12/site-packages/yaml/constructor.py - /usr/lib64/python3.12/site-packages/yaml/cyaml.py - /usr/lib64/python3.12/site-packages/yaml/dumper.py - /usr/lib64/python3.12/site-packages/yaml/emitter.py - /usr/lib64/python3.12/site-packages/yaml/error.py - /usr/lib64/python3.12/site-packages/yaml/events.py - /usr/lib64/python3.12/site-packages/yaml/loader.py - /usr/lib64/python3.12/site-packages/yaml/nodes.py - ... and 8 more Remediation: [hint] Remove third-party target Python 3.12 packages before attempting the upgrade or ensure that those modules are not interfering with distribution-provided modules. Key: 540ad84e3486eeb475fc8ce00450e75dadb956c8 ---------------------------------------- Risk Factor: high Title: Packages not signed by the distribution vendor found on the system Summary: The official solution for in-place upgrades contains instructions for the migration of packages signed by the vendor of the system distribution. Third-party content is not known to the upgrade process and it might need to be handled extra. Third-party packages may be removed automatically during the upgrade if they depend on official distribution content which is not present on the target system - therefore RPM dependencies of such packages cannot be satisfied and hence such packages cannot be installed on the target system. The following packages have not been signed by the vendor of the distribution: - leapp - leapp-deps - leapp-upgrade-el9toel10 - leapp-upgrade-el9toel10-deps - leapp-upgrade-el9toel10-fapolicyd - python3-leapp - python3.12-pyyaml - snactor Related links: - Handling the migration of your custom and third-party applications: https://red.ht/customize-rhel-upgrade-actors Remediation: [hint] The most simple solution that does not require additional knowledge about the upgrade process is the uninstallation of such packages before the upgrade and installing these (or their newer versions compatible with the target system) back after the upgrade. Also you can just try to upgrade the system on a testing machine (or after the full system backup) to see the result. However, it is common use case to migrate or upgrade installed third party packages together with the system during the in-place upgrade process. To examine how to customize the process to deal with such packages, follow the documentation in the attached link for more details. Key: 13f0791ae5f19f50e7d0d606fb6501f91b1efb2c ---------------------------------------- Risk Factor: medium Title: Berkeley DB (libdb) has been detected on your system Summary: Libdb was marked as deprecated in RHEL-9 and in RHEL-10 is not included anymore. There are a couple of alternatives in RHEL-10; the applications that depend on libdb will not work. Such applications must implement another type of backend storage. And migrate existing data to the new database format. Related links: - Migrating to a RHEL 10 without libdb: https://access.redhat.com/articles/7099256 Remediation: [hint] Back up your data before proceeding with the data upgrade/migration. For the conversion, the tool db_converter from the libdb-utils rpm could be used. This database format conversion must be performed before the system upgrade. The db_converter is not available in RHEL 10 systems. For more information, see the provided article. Key: fdc8f5b084e95922a4f59485a807a92cae2fc738 ---------------------------------------- Risk Factor: low Title: SElinux will be set to permissive mode Summary: SElinux will be set to permissive mode. Current mode: enforcing. This action is required by the upgrade process to make sure the upgraded system can boot without beinig blocked by SElinux rules. Remediation: [hint] Make sure there are no SElinux related warnings after the upgrade and enable SElinux manually afterwards. Notice: You can ignore the "/root/tmp_leapp_py3" SElinux warnings. Key: 39d7183dafba798aa4bbb1e70b0ef2bbe5b1772f ---------------------------------------- Risk Factor: low Title: The subscription-manager release is going to be kept as it is during the upgrade Summary: The upgrade is executed with the --no-rhsm option (or with the LEAPP_NO_RHSM environment variable). In this case, the subscription-manager will not be configured during the upgrade. If the system is subscribed and release is set already, you could encounter issues to get RHEL content using DNF/YUM after the upgrade. Remediation: [hint] Set the new release (or unset it) after the upgrade using subscription-manager: subscription-manager release --set 10.0 Key: 01986584e27e85ea18929586faf614eee011a121 ---------------------------------------- Risk Factor: info Title: Excluded target system repositories Summary: The following repositories are not supported by Red Hat and are excluded from the list of repositories used during the upgrade. - codeready-builder-for-rhel-10-s390x-eus-rpms - codeready-builder-for-rhel-10-aarch64-rpms - codeready-builder-for-rhel-10-s390x-rpms - codeready-builder-beta-for-rhel-10-aarch64-rpms - codeready-builder-for-rhel-10-aarch64-eus-rpms - codeready-builder-beta-for-rhel-10-ppc64le-rpms - codeready-builder-for-rhel-10-x86_64-rpms - codeready-builder-for-rhel-10-ppc64le-rpms - codeready-builder-beta-for-rhel-10-x86_64-rpms - codeready-builder-for-rhel-10-x86_64-eus-rpms - crb - codeready-builder-for-rhel-10-rhui-rpms - codeready-builder-for-rhel-10-ppc64le-eus-rpms - codeready-builder-beta-for-rhel-10-s390x-rpms - rhui-codeready-builder-for-rhel-10-aarch64-rhui-rpms - rhui-codeready-builder-for-rhel-10-x86_64-rhui-rpms Remediation: [hint] If some of excluded repositories are still required to be used during the upgrade, execute leapp with the --enablerepo option with the repoid of the repository required to be enabled as an argument (the option can be used multiple times). Key: 1b9132cb2362ae7830e48eee7811be9527747de8 ---------------------------------------- Risk Factor: info Title: SElinux relabeling will be scheduled Summary: SElinux relabeling will be scheduled as the status is permissive/enforcing. Key: 8fb81863f8413bd617c2a55b69b8e10ff03d7c72 ----------------------------------------