Upgrading from RHEL 7.9 to 8.2 using Leapp - Error
====> * removed_pam_modules_scanner
Scan PAM configuration for modules that are not available in RHEL-8.
====> * common_leapp_dracut_modules
Influences the generation of the initram disk
====> * multipath_conf_read
Reads multipath configuration files (multipath.conf, and any files in
====> * get_installed_desktops
Actor checks if kde or gnome desktop environments
====> * spamassassin_config_read
Reads spamc configuration (/etc/mail/spamassassin/spamc.conf), the
====> * system_facts
Provides data about many facts from system.
====> * network_manager_read_config
Provides data about NetworkManager configuration.
====> * sssd_facts
Check SSSD configuration for changes in RHEL8 and report them in model.
====> * storage_scanner
Provides data about storage settings.
====> * used_repository_scanner
Scan used enabled repositories
====> * repositories_blacklist
Generate list of repository IDs that should be ignored by Leapp during upgrade process
====> * vsftpd_config_read
Reads vsftpd configuration files (/etc/vsftpd/*.conf) and extracts necessary information.
====> * rpm_transaction_config_tasks_collector
Provides additional RPM transaction tasks from /etc/leapp/transaction.
====> * ipa_scanner
Scan system for ipa-client and ipa-server status
====> * quagga_daemons
Active quagga daemons check.
====> * selinuxcontentscanner
Scan the system for any SELinux customizations
====> * sctp_read_status
Determines whether or not the SCTP kernel module might be wanted.
====> * xfs_info_scanner
This actor scans all mounted mountpoints for XFS information
====> * pes_events_scanner
Provides data about packages events from Package Evolution Service.
====> * setuptargetrepos
Produces list of repositories that should be available to be used by Upgrade process.
============================================================
ERRORS
2020-12-24 10:52:30.537606 [ERROR] Actor: repository_mapping
Message: The repository mapping file not found (/etc/leapp/files/repomap.csv).
Summary:
Hint: Read documentation at the following link for more information about how to retrieve the valid file: https://access.redhat.com/articles/3664871
============================================================
END OF ERRORS
============================================================
UPGRADE INHIBITED
Upgrade has been inhibited due to the following problems:
1. Inhibitor: Missing/Invalid PES data file (/etc/leapp/files/pes-events.json)
Consult the pre-upgrade report for details and possible remediation.
============================================================
UPGRADE INHIBITED
Debug output written to /var/log/leapp/leapp-upgrade.log
============================================================
REPORT
A report has been generated at /var/log/leapp/leapp-report.json
A report has been generated at /var/log/leapp/leapp-report.txt
============================================================
END OF REPORT
Answerfile has been generated at /var/log/leapp/answerfile
Responses
Hello Ankit,
Please check the error report/log files over there and that should provide a clue/reason for the error. Also, follow all the pre-requisites before initiating the leapp-upgrade process. There are some additional files required for the upgrade which you would need to manually download and make it available at the required location. Please report back with error log details for further help.
Hello Ankit,
As per your error, it is missing required files, follow below procedure on your VM and try again:
tar -xzf leapp-data14.tar.gz -C /etc/leapp/files && rm leapp-data14.tar.gz
Guru
23293 points
Thanks for the input here "Hermant Gangwar"
It appears this discussion was started in December of 2020, and yours is the last update, some 10 months or so later, and Ankit never replied in the discussion, I hope he got this resolved.
Regards,
RJ
Pro
574 points
AAAAAAH.
I've just hit this error on several machines, after successfully upgrading one by hand, and then ansibling all the steps. Turns out i missed the step to deploy the leapp-data tarfile,when doing my ansible.
So, instead of a sensible message saying those files were not there, instead, i get network connection errors, sending me down a wormhole of looking into proxy configurations, and past bugs in which leapp couldnt get through NTLM proxies and so on.
All i needed was an error message saying the required files were not there, and then exit, without the spurious network errors to mislead me. So, THANKS AGAIN REDHAT, for a completely mind-buggering customer experience.
anyone have this message ..
Upgrade has been inhibited due to the following problems: 1. Inhibitor: Incompatible Leapp data assets are present Consult the pre-upgrade report for details and possible remediation.
the /etc/leapp/files/device_driver_deprecation_data.json are download version leapp-data-19.tar.gz
Hi
I am getting below error when I try to upgrade from RHEL 7.6 to RHEL 8[of any available version]
2023-07-13 12:46:21.000131 [ERROR] Actor: repository_mapping Message: The repository mapping file not found (/etc/leapp/files/repomap.csv). Summary: Hint: Read documentation at the following link for more information about how to retrieve the valid file: https://access.redhat.com/articles/3664871
tar -xzvf leapp-data-22.tar.gz -C /etc/leapp/files/device_driver_deprecation_data.json pes-events.json repomap.json
cd /etc/leapp/files/ lsdevice_driver_deprecation_data.json pes-events.json repomap.json #
My RHEL server is a AWS instance and no RHSM. Hence I used the following command to upgrade,
leapp preupgrade --no-rhsmAppreciate if I get any help.
do we have leapp-data-23.tar.gz yet? am getting below error using leapp-data-22.tar.gz 2023-11-18 00:24:29.400924 [ERROR] Actor: repository_mapping Message: The repository mapping file is invalid: The obtained repomap data has unsupported version of format. Get 1.0.0 required 1.2.0
You don't need to worry about the leapp-data files any more because it is included in the latest leapp-repository package. You may need to reinstall the leapp packages if you have manually installed a leapp-data file.
Can anyone helps me on this???
Following errors occurred and the upgrade cannot continue:
1. Actor: repository_mapping
Message: The repository mapping file is invalid: The obtained repomap data has unsupported version of format. Get 1.0.0 required 1.2.0
2. Actor: repositories_blacklist
Message: Actor didn't receive required messages: RepositoriesMapping
3. Actor: pes_events_scanner
Message: Cannot parse RepositoriesMapping data properly
Please find the leapp-report.txt file. Even I reinstalled the "leapp-upgrade-el7toel8 rpm", I am getting this error.
cat /var/log/leapp/leapp-report.txtRisk Factor: high (error) Title: The repository mapping file is invalid: The obtained repomap data has unsupported version of format. Get 1.0.0 required 1.2.0
Summary: {"hint": "All official data files are nowadays part of the installed rpms. This issue is usually encountered when the data files are incorrectly customized, replaced, or removed (e.g. by custom scripts). In case you want to recover the original file, remove it (if still exists) and reinstall the leapp-upgrade-el7toel8 rpm."}Risk Factor: high (error) Title: Actor didn't receive required messages: RepositoriesMapping
Summary:Risk Factor: high (error) Title: Cannot parse RepositoriesMapping data properly Summary: {"Problem": "Did not receive a message with mapped repositories"}
Found the work around and still using leapp-data-22. Until the new Tar file comes out do the following. This worked for me......When installing LEAPP install it by using the previous version. It will install the dependencies that support this version: - leapp-upgrade-el7toel8-0.18.0-3.el7_9 - leapp-upgrade-el7toel8-deps-0.18.0-3.el7_9 - leapp-0.15.1-1.el7_9 - leapp-deps-0.15.1-1.el7_9
Once installed proceed as normal.
-Harvey Robinson Senior Systems Engineer
I tried what you have suggested. But getting this yum error.
Message: Unable to use yum successfully Summary: Details: Command ['systemd-nspawn', '--register=no', '--quiet', '-D', '/var/lib/leapp/scratch/mounts/root_/system_overlay', '--setenv=LEAPP_UPGRADE_PATH_TARGET_RELEASE=8.8', '--setenv=LEAPP_NO_RHSM=0', '--setenv=LEAPP_EXPERIMENTAL=0', '--setenv=LEAPP_UPGRADE_PATH_FLAVOUR=default', '--setenv=LEAPP_COMMON_TOOLS=:/etc/leapp/repos.d/system_upgrade/common/tools:/etc/leapp/repos.d/system_upgrade/el7toel8/tools', '--setenv=LEAPP_COMMON_FILES=:/etc/leapp/repos.d/system_upgrade/common/files:/etc/leapp/repos.d/system_upgrade/el7toel8/files', '--setenv=LEAPP_IPU_IN_PROGRESS=7to8', '--setenv=LEAPP_UNSUPPORTED=0', '--setenv=LEAPP_EXECUTION_ID=8c0c5b52-2c16-4a53-a293-873974bdbd0f', '--setenv=LEAPP_HOSTNAME=xxxxxxxxxxxxxxx', 'yum', 'clean', 'all'] failed with exit code 1. Stderr: Host and machine ids are equal (faaffc2288694dd0aa51a47f2643e83d): refusing to link journals There are no enabled repos. Run "yum repolist all" to see the repos you have. To enable Red Hat Subscription Management repositories: subscription-manager repos --enable To enable custom repositories: yum-config-manager --enable
I'm getting the same error. New version of leapp just came out. What I'm doing for the work around is installing leapp-upgrade-el7toel8-0.18.0-3.el7_9 / leapp-upgrade-el7toel8-deps-0.18.0-3.el7_9 and still using leapp-data-22.
They have version 19 now out but no leapp-data-23 yet. So specify the version of the package until the new TAR is released.
Well it will only work if you use ALL of the previous versions of leapp including the generic LEAPP. I'm still experiencing the issue. Same error.
Found the work around and still using leapp-data-22. Until the new Tar file comes out do the following. This worked for me......When installing LEAPP install it by using the previous version. It will install the dependencies that support this version: - leapp-upgrade-el7toel8-0.18.0-3.el7_9 - leapp-upgrade-el7toel8-deps-0.18.0-3.el7_9 - leapp-0.15.1-1.el7_9 - leapp-deps-0.15.1-1.el7_9
Once installed proceed as normal.
-Harvey Robinson Senior Systems Engineer
No need the older leapps. we can upgrade hosts with the available leapp version.
I have mentioned the target version of the upgrade. Then only it's upgraded of all my 3 machines.
leapp preupgrade --target 8.8 leapp upgrade --target 8.8Thanks Harvey Robinson for your support :)
No problem....I've created an upgrade Playbook and Post upgrade playbook that runs in a workflow. And I have accounterred many different errors and issues. I've created multiple content views already for 8.6 to work successfully for automation. It's better for me to hard lock the version to 8.6 and use the previous version of LEAPP. During the post upgrade it updates everything to the most current version of RHEL 8, so to 8.9. So I'm good as is..... I'm glad you found the issue that it's looking for a locked version of 8.8 instead.
- Harvey Robinson
Below was my version of files with leapp-data-22.tar.gz. ]# yum list installed |grep leapp leapp.noarch 0.16.0-1.el7_9 @extras leapp-deps.noarch 0.16.0-1.el7_9 @extras leapp-rhui-aws.noarch 1.0.7-1.el7 @config leapp-upgrade-el7toel8.noarch 0.19.0-1.el7_9 @extras leapp-upgrade-el7toel8-deps.noarch python2-leapp.noarch 0.16.0-1.el7_9 @extras
and i performed below commands yum downgrade leapp-upgrade-el7toel8.noarch leapp-upgrade-el7toel8-deps.noarch yum downgrade python2-leapp.noarch leapp.noarch =====i got below after downgrad commands== [root@kadaasstgldgin01aipu leapp]# yum list installed |grep leapp leapp.noarch 0.15.0-1.el7_9 @extras leapp-deps.noarch 0.15.1-1.el7_9 @extras leapp-rhui-aws.noarch 1.0.7-1.el7 @config leapp-upgrade-el7toel8.noarch 0.18.0-3.el7_9 @extras leapp-upgrade-el7toel8-deps.noarch python2-leapp.noarch 0.15.0-1.el7_9 @extr then i tried again leapp upgrade --target 8.8 --no-rhsm and the upgrade passed. I literally just finished my upgrade.
The tar ball extraction is not likely necessary anymore. This step might be added into SOP of many users due to force of habit. Please remove the wget and tar extract step from your checklist. We have incorporated that with newer version of leapp. So the reinstallation of leapp-upgrade-el7toel8.noarch should fix the issue. See: leapp fails with "The repository mapping file is invalid: The obtained repomap data has unsupported version of format. Get 1.0.0 required 1.2.0" https://access.redhat.com/solutions/7047298
No problem....I've created an upgrade Playbook and Post upgrade playbook that runs in a workflow. And I have accounterred many different errors and issues. I've created multiple content views already for 8.6 to work successfully for automation. It's better for me to hard lock the version to 8.6 and use the previous version of LEAPP. During the post upgrade it updates everything to the most current version of RHEL 8, so to 8.9. So I'm good as is..... I'm glad you found the issue that it's looking for a locked version of 8.8 instead.
Harvey Robinson