Chapter 7. Troubleshooting conversions This chapter lists troubleshooting resources and tips. 7.1. Troubleshooting resources To help you troubleshoot issues that can occur during the conversion process, review the log messages that are printed to the console and log files. Console Output By default, only info, warning, error, and critical log level messages are printed to the console output by the Convert2RHEL utility. To also print debug messages, use the --debug option with the convert2rhel command. Logs The /var/log/convert2rhel/convert2rhel.log file lists debug, info, warning, error, and critical messages. The /var/log/convert2rhel/rpm_va.log file lists all package files on the unconverted system that a user has modified. This output is generated by the rpm -Va command, which is run automatically unless the --no-rpm-va option is used with the convert2rhel command. 7.2. Fixing dependency errors During a conversion from a different Linux distribution to RHEL, certain packages might be installed without some of their dependencies. Prerequisites You have successfully completed the conversion to RHEL. See Converting to a RHEL system for more information. Procedure Identify dependencies errors: If the command displays no output, no further actions are required. To fix dependency errors, reinstall the affected packages. During this operation, the yum utility automatically installs missing dependencies. If the required dependencies are not provided by repositories available on the system, install those packages manually. 7.3. Troubleshooting issues with Red Hat Insights conversions The following issues might occur when using Red Hat Insights to convert to RHEL. 7.3.1. Missing systems in pre-conversion analysis task When running the Pre-conversion analysis for converting to RHEL task in Red Hat Insights, CentOS Linux 7 systems that appeared correctly in RHEL Inventory might not appear in the list of available systems to run the pre-conversion analysis on. This issue occurs when the Remote Host Configuration (RHC) is disconnected. Procedure Log in to the Red Hat Hybrid Cloud Console and go to Red Hat Insights > RHEL > Inventory > Systems . Select the affected system from the table. In the General Information tab, go to the System Status card and verify the RHC status: If the RHC status is Connected , RHC is connected correctly. If the RHC status is Not available , RHC is disconnected. Proceed to the step to reconnect RHC. Unregister the system in your terminal: To help with troubleshooting, set the RHC systemd service ( rhcd ) logging to the highest level: Register your system with Red Hat Insights and re-enable RHC in your terminal: Replace activation_key and organization_ID with the activation key and organization ID from the Red Hat Customer Portal. Verification Verify that you can select the system in the Pre-conversion analysis for converting to RHEL task. If the system still does not appear correctly, review error messages from rhcd and the insights-client tool: 7.3.2. Pre-conversion analysis task fails to complete After running the Pre-conversion analysis for converting to RHEL task, one or more of the systems can fail to generate a report with the error message Task failed to complete for an unknown reason. Retry this task at a later time. If this issue occurs, complete the steps below to troubleshoot. Procedure Verify if the affected system is unavailable, for example because of a network accessibility issue or because the system is shut off. Review the RHC systemd service ( rhcd ) for errors: Stop rhcd in your terminal: Set rhcd logging to the highest level: Restart rhcd : Review error messages posted by rhcd : Review the rhc-worker-script log file for errors: 7.4. Known issues and limitations The following issues and limitations are known to occur during the conversion: Systems that connect to the Internet using an HTTP proxy server cannot convert using Red Hat CDN or Satellite through RHSM by using the command line. To work around this problem, enable HTTP proxy for yum and then configure the HTTP proxy for RHSM: Configure yum to use an HTTP proxy. For more information, see the Red Hat Knowledgebase solution How to enable proxy settings for yum command on RHEL? Install the subscription-manager package: Download the Red Hat GPG key: Install a repository file for the client-tools repository that contains the subscription-manager package: conversions to RHEL 7: For conversions to RHEL 8: For conversions to RHEL 9: If you are converting to an earlier version of RHEL 8, for example, RHEL 8.5, update the USDreleasever value in the client-tools repository: Replace release_version with the correct release version, for example 8.5 or 8.8 . Install the following subscription-manager packages: Configure HTTP proxy for RHSM. For more information, see the Red Hat Knowledgebase solution How to configure HTTP Proxy for Red Hat Subscription Management . Register the system with RHSM: Replace organization_id and activation_key with the organization ID and activation key from the Red Hat Customer Portal. Remove the organization ID and activation key from the /etc/convert2rhel.ini file. Perform the conversion to RHEL: ( RHELC-559 ) UEFI systems with Secure Boot enabled are not supported for conversion. To work around this issue, complete the following steps: Disable Secure Boot before the conversion. For more information, see the Red Hat Knowledgebase solution convert2rhel fails on UEFI systems with Secure Boot enabled . Perform the conversion to RHEL. If converting from Oracle Linux 7 or Alma Linux 8, install the shim-x64 package: Re-enable Secure Boot. ( RHELC-138 ) If you are converting by using Red Hat Insights, running two RHC daemon (rhcd) processes simultaneously prevents the pre-conversion analysis from running as expected. To prevent this issue, run only one rhcd process at a time. ( HMS-2629 ) 7.5. Obtaining support If you experience problems during the conversion, notify Red Hat so that these problems can be addressed. Important If you are experiencing problems during the conversion, raise a Support case of Severity 3 or Severity 4 level only. For more details, see Production Support Terms of Service . Prerequisites The sos package is installed. You must use this package to generate an sosreport that is required when opening a support case for the Red Hat Support team. Procedure To obtain support, perform either of the following steps: Open a support case: Select the appropriate version of RHEL as the product, and provide an sosreport from your system. Generate an sosreport on your system: Note that you can leave the case ID empty. Submit a bug report : Open a bug, select the appropriate version of RHEL as the product, and select convert2rhel as the component. For details on generating an sosreport , For more information, see the Red Hat Knowledgebase solution What is an sosreport and how to create one in Red Hat Enterprise Linux? . For more information about opening and managing a support case on the Customer Portal, see the article How do I open and manage a support case on the Customer Portal? . For information about Red Hat's support policy for Linux distribution conversions, see Convert2RHEL Support Policy .

Commands:
yum check dependencies
rhc disconnect
sed -ie 's%error%trace%' /etc/rhc/config.toml
insights-client --register rhc connect -a <activation_key> -o <organization_ID>
journalctl -u rhcd less /var/log/insights-client/insights-client.log
systemctl stop rhcd
sed -ie 's%error%trace%' /etc/rhc/config.toml
systemctl start rhcd
journalctl -u rhcd
less /var/log/rhc-worker-script/rhc-worker-script.log
curl -o /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release https://security.access.redhat.com/data/fd431d51.txt
curl -o /etc/yum.repos.d/client-tools.repo https://cdn-public.redhat.com/content/public/repofiles/client-tools-for-rhel-7-server.repo
curl -o /etc/yum.repos.d/client-tools.repo https://cdn-public.redhat.com/content/public/repofiles/client-tools-for-rhel-8.repo
curl -o /etc/yum.repos.d/client-tools.repo https://ftp.redhat.com/redhat/client-tools/client-tools-for-rhel-9.repo
sed -i 's%\USDreleasever% <release_version> %' /etc/yum.repos.d/client-tools.repo
yum -y install subscription-manager subscription-manager-rhsm-certificates
subscription-manager register --org <organization_id> --activationkey <activation_key>
convert2rhel
yum install -y shim-x64
sosreport