Leapp utility metadata in-place upgrades of RHEL for disconnected upgrades (including Satellite)

Updated

Disclaimer

Leapp data files are now a part of the leapp-repository package. Therefore, you no longer need to manually download these files.

IMPORTANT: Leapp data files mentioned in this article are outdated. The content of this article is temporarily preserved for reference.

Before upgrading, update to the latest packages available for your system version. Data files are now present in the following RPMs:

Environments

  • Red Hat Enterprise Linux (RHEL) 7
  • Red Hat Enterprise Linux (RHEL) 8
  • Red Hat Enterprise Linux (RHEL) 9

What is this metadata?

IMPORTANT: If you are using RHEL 7.6 for IBM POWER 9 (little endian) or IBM Z (structure A) architectures, follow the Leapp data snapshots for an in-place upgrade Knowledgebase article instead.

This metadata provides updated information required by the Leapp tool to perform in-place upgrades. The metadata includes a variety of important information about hardware deprecation and enablement, as well as the evolution of RPM packages and content repositories that change over time, such as renames, splits, merges, moves, and similar events. This data is frequently changing and may be extended in the future to include additional information to improve the in-place upgrade process. Some of this information does not have corresponding equivalents in RPM package metadata. Some information relates uniquely to how RHEL productizes and distributes content in different product repositories. Some information may relate to deprecation and support status based on partner agreements, unique to Red Hat. Therefore, some of the metadata may not apply or correctly describe other linux distributions.

For systems that have network isolation making this service API query (https://cert.cloud.redhat.com/api/pes/repomap.json) impossible, this article explains how to download the metadata so that the upgrade process can continue. This is further documented in Chapter 3.1. Preparing a RHEL 7 system for the upgrade for the in-place upgrade from RHEL 7 to RHEL 8, or Chapter 3.1. Preparing a RHEL 8 system for the upgrade for the in-place upgrade from RHEL 8 to RHEL 9.

The metadata includes the following copyright notice:

"legal_notice": "Copyright 2018 Red Hat, Inc. This file is provided to customers as a part of the Services under the Red Hat Enterprise Agreement and is not for redistribution."

Instructions on how to use this metadata

For a successful in-place upgrade of RHEL versions supported by the Leapp utility, the data file attached to this article must be extracted into the /etc/leapp/files/ directory on the target system.

The data files include RPM package changes (pes-events.json), RPM repository mapping (repomap.json), and information about removed or unsupported kernel drivers (device_driver_deprecation_data.json) .

Note: Please ensure you are always using the latest builds of leapp and leapp-repository packages.

Download the attached file leapp-data-22.tar.gz (SHA-256 checksum: 6afda63f00dbcb5a45434b1e120eb31d35574acf2bc9cce5537259c8cedb01f4) to /etc/leapp/files/ and extract it:

# tar -xzf leapp-data-22.tar.gz -C /etc/leapp/files && rm leapp-data-22.tar.gz

For complete instructions on how to perform an in-place upgrade to RHEL 8, see Upgrading from RHEL 7 to RHEL 8.

For complete instructions on how to perform an in-place upgrade to RHEL 9, see Upgrading from RHEL 8 to RHEL 9.

Community Linux distributions

The upstream project for Leapp has provided guidance on how community distributions derived from RHEL can reproduce similar metadata that more accurately represent the community distributions. This guidance and documentation can be found at Content from leapp.readthedocs.io is not included.Welcome to developer documentation for Leapp!

SBR
Product(s)
Category
Components
Tags
Article Type