{"id":105498,"date":"2025-03-12T12:09:04","date_gmt":"2025-03-12T04:09:04","guid":{"rendered":"https:\/\/version-2.com\/?p=105498"},"modified":"2025-03-24T12:40:23","modified_gmt":"2025-03-24T04:40:23","slug":"planning-a-centos-to-rocky-linux-migration","status":"publish","type":"post","link":"https:\/\/version-2.com\/zh\/2025\/03\/planning-a-centos-to-rocky-linux-migration\/","title":{"rendered":"Planning a CentOS to Rocky Linux Migration"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/p>

On June 30, 2024, the ten-year run of CentOS 7<\/a> came to an end, but more significantly, the date marked all versions of <\/span>CentOS Linux<\/span><\/a> reaching end of life<\/span>. Now, more than six months later, many organizations are still planning their migrations to other community-supported Enterprise Linux distributions<\/a>. They are exploring CentOS alternatives<\/a> in the hopes avoiding the squeeze from Red Hat and having to pay for Extended Life Cycle Support, on top of RHEL licenses for each host that needs to be kept secure (which is usually all of them).<\/p>

One popular migration path is CentOS to Rocky Linux<\/a>. In other blogs, we\u2019ve looked at why many have chosen Rocky Linux, but here, we’ll focus on the primary considerations for organizations that haven\u2019t made the move yet, highlight potential risks, and explain how to evaluate the readiness of a given enterprise architecture to move from one major Enterprise Linux version (6, 7, and 8) to the latest version, Enterprise Linux 9. We’ll also provide a step-by-step walkthrough of a CentOS 7 to Rocky Linux 9 migration.<\/p><\/div>

\u00a0<\/p>

Step 1: Evaluate Whether Your Applications Are Ready for Rocky Linux Migration<\/h2>

How were you made aware that your team has out-of-compliance, End-of-Life CentOS hosts in their architecture in the first place? Perhaps your IT department sent you a email containing a list of these hosts, as the result of a scan. Or maybe you examined a list of AMIs in your Amazon Web Services (AWS) EC2 infrastructure, and came up with a list of affected hosts. Whatever way it happened, you have the list of hosts that need an upgrade, which means you have essentially completed the first step for migration: creating an inventory of hosts that need to make the move to Rocky Linux.<\/p>

Ideally, you have a list of applications that are running on each of these hosts, and know the purpose of each. For example, \u201cThis one is a MariaDB<\/a> server,\u201d or \u201cThis runs Oracle 12c.\u201d If you don\u2019t, now is a good time to start building out a spreadsheet listing the CentOS hosts that need to be upgraded that includes the workload each is responsible for. Then create another inventory, for each host, of what software is installed. Find the owners of each machine, so that you can further examine what software is installed, perhaps in unconventional ways, that you might be missing.<\/p>

Without knowing what software is on which machines, you won\u2019t know the side effects of completing a major Enterprise Linux version upgrade. The main side effect of upgrading is new versions of the kernel, new versions of software in the yum \/ dnf repositories, and new versions of glibc and libstdc++. And this side effect can have some major unintended consequences.<\/p>

Step 2: Decide Between Migrating in Place vs. Building a New System<\/h2>

The major consequences listed above are particularly important when deciding whether to do an in-place upgrade, or building a new system. You can either migrate a system to Rocky Linux in-place, or build a new system and migrate applications and data over. Each option has pros and cons, but let\u2019s examine the three side effects of upgrading: new kernel, new versions of dnf-sourced applications, and new API and ABI versions.<\/p>

To be clear, it\u2019s not just the ABI contracts of glibc and libstdc++ that can stymie your upgrade plans. All bets are off regarding API and ABI compatibility between all libraries and packages between major versions of EL.\u202fAnother risk of in-place upgrades is, in the end, the system may have a combination of packages from different EL versions; a few libraries from EL7 and an app from EL8 running on an EL9 box.\u202fHybrid-version systems are incredibly difficult to troubleshoot, or even rebuild if not restoring from a full backup.<\/p>

When you examine your inventory of hosts that need to be migrated off of CentOS, you need to determine if they\u2019re bare-metal. Physical hosts are much more likely to have custom kernel modules or drivers built against the current kernel against source, source that\u2019s often proprietary. Perhaps the host is connected to a tape library, has a PCI-E card like a graphics card, or has another peripheral that\u2019s connected to an industrial application from a third-party manufacturer. For this reason, a hardware inventory is incredibly important: what peripherals or non-standard hardware are installed in the host?<\/p>

Most open source drivers and kernel modules are going to seamlessly work from one major EL release to another, but add-ons that aren\u2019t shipped with the server are more likely to need a driver to be recompiled against the new kernel in Rocky Linux. Make sure you can both obtain the source code for the driver and that it compiles against the new kernel. Otherwise you might successfully upgrade to Rocky Linux, but be stuck with an application that can\u2019t reach a critical peripheral.<\/p>

If you are on physical hardware as described above, migrating in place has the advantage that you don’t need more systems. This may be the easiest (and least expensive) route. You do have to make sure that connections are stable, and the machine will be available the whole time, because if the upgrade script is interrupted, the system may be left in an unrecoverable state. This would probably require a rescue disk and some manual work to get to a point where it is usable again. If you can’t take a system out of production to rebuild, then running the migration may be the best option, as the migration can be planned in a standard maintenance window.<\/p>

However, if you are on a virtualized infrastructure, or have spare hardware, it would be safer to build a new system as you want it, then migrate the data and applications over and swap out the old system with the new. But even then, a software inventory is especially important due to the upgraded dnf-sourced software and upgraded glibc\/libstdc++ libraries.<\/p>

Step 3: Use a Software Inventory to Mitigate Risk<\/h2>

If your organization produces software with C++, it\u2019s possible that you\u2019re producing applications \u201cdynamically linked\u201d against system libraries. If you\u2019re targeting CentOS 7, and you upgrade to Rocky Linux 9<\/a>, the libraries you linked against are going to be upgraded, and the application you wrote might suddenly crash at runtime, even if it starts successfully after the upgrade.<\/p>

This is because certain standard library methods might remain the same, allowing the application to start, but others might have been deprecated or changed, causing the application to crash when they\u2019re no longer available. Because these safety checks are completed at compile-time, a runtime error might occur.<\/p>

Even if your organization doesn\u2019t maintain their own C++ applications, you might be installing applications from a third-party vendor that link against CentOS 7 libraries. If this vendor uses an external yum or dnf-based repository, there\u2019s a good chance that the upgrade to Rocky might fail due to unresolved dependency issues. If the application is installed by downloading a .tar.gz, .sh, or .run file, and binaries are installed onto the host from that installer, there\u2019s a strong possibility that the application might suffer similar crashes or incompatibilities from unexpected versions of C++ libraries, Python bindings, Lua versions, and the list goes on.<\/p>

All of the above illustrates why it’s so important to have a software inventory of some kind. It could be as simple as a spreadsheet or a Software Bill of Materials (SBOM)<\/a>. Once you have that inventory, you can plan ahead and contact the vendors of third-party software, making sure they have an EL 8 or EL9 version of their software that can be upgraded to once your host becomes a Rocky Linux host.<\/p>

As for the dnf-sourced packages, and considering the previously mentioned issues with version numbers changing for supporting libraries, moving from CentOS 7 to Rocky Linux 9 can include some major upgrades. For example, the upgrade from MariaDB 5.5, which was released in April 2012, to MariaDB 10.5.27, which shipped in May 2023. As you can imagine, there needs to be an end-to-end plan for this upgrade, and all of the hard-to-predict “ripples” it may cause.<\/p>

What happens when you run into applications that can\u2019t run on the new version of Rocky 8 or Rocky 9? One option would be containerizing old workloads in order to increase security, reducing the attack surface by running in an isolated container running on an up-to-date Rocky 9 host.<\/p>

Migration Services and Technical Support for Rocky Linux<\/h3>

Get assistance from Enterprise Architects who are directly involved with the Rocky Linux project.<\/p>

Talk to a Rocky Linux Expert\u00a0<\/span><\/a><\/p><\/blockquote>

Step 4: Determine Your CentOS to Rocky Linux Migration Path<\/h2>

There are a few considerations teams will need to make when migrating from CentOS to Rocky Linux. Depending on the CentOS version(s) being used, the upgrade path may require migrating to intermediary versions before arriving at the intended version. (E.g., CentOS 6 to CentOS 7, CentOS 7 to CentOS 8, CentOS 8 to Rocky Linux 8, then Rocky Linux 8 to Rocky Linux 9).<\/p>

Approaching your upgrade with this step-wise approach is also useful for mitigating the risks described above. Catching incompatibilities early on in the upgrade process will be critical for informing leadership of how long this process is actually going to take.<\/p>

Migrating CentOS 6 to Rocky Linux<\/h3>

Unfortunately, there is no direct migration path from CentOS 6 to Rocky Linux. Rocky Linux starts at 8, so hosts will have to be on CentOS 8 to migrate. As described above, there are too many changes between CentOS 6 and 7, much less 8, to migrate. Once you’ve migrated to CentOS 7 you can migrate from CentOS 7 to CentOS 8 then migrate to Rocky Linux 9, or migrate from CentOS 8 to Rocky Linux 8 then upgrade to Rocky Linux 9.<\/p>

For CentOS 6 users there are two ways to do this.<\/p>

  1. Upgrade from CentOS 6, to 7, to 8, then migrate to Rocky Linux 8, then upgrade to Rocky Linux 9. This process can take a considerable amount of time, and can run into some additional hiccups due to the package changes between major versions.<\/li>
  2. Build a new machine and migrate your data over.\u202fThe best case scenario with this approach is that all third party software needed in the new machine has a new version, and all your data can be upgraded safely. The worst case is that you’ll have software with no new version and will need to find alternatives or find a way to run the software anyway. This depends on the libraries being used in your CentOS 6 install. Luckily, containerization makes it easy to run older versions of software on newer systems, or even on completely different distributions entirely.<\/li><\/ol>

    Migrating CentOS 7 to Rocky Linux<\/h3>

    The migration path for CentOS 7 to Rocky Linux is similar to CentOS 6. However, migrating from CentOS 7 to Rocky Linux is a bit easier because CentOS 7 already uses systemd for service management, while CentOS 6 still uses legacy SysV init scripts.<\/p>

    There are a few other changes to keep an eye out for when moving from CentOS 7 to Rocky Linux, but, aside from the service management difference, the considerations are nearly identical to CentOS 6 migration.<\/p>

    Video: CentOS 7 Migration Recommendations<\/p>

    \u00a0<\/div><\/div><\/div><\/article><\/blockquote>

    Migrating CentOS 8 to Rocky Linux<\/h3>

    Migrating from CentOS 8 to Rocky Linux 8 is relatively painless, and avoids all of the risks described above. Since it is nearly identical, there are only a few changes, which makes this the least risky and easiest to validate step in the process. The repos are swapped out for Rocky Linux repos, and a few packages are replaced (mostly branding packages, for example, the package that provides all of the logos for CentOS).<\/p>

    Real-World Example: Upgrading CentOS 7 to Rocky Linux 9<\/h2>

    In this section, we will walk through a CentOS 7 to Rocky Linux 9 migration, showing all the steps involved and potential trouble spots.<\/p>

    1. Install the Latest Version of the ELevate Repository from the AlmaLinux Project<\/h3>

    $ yum install -y http:\/\/repo.almalinux.org\/elevate\/elevate-release-latest-el$(rpm<\/a> –eval %rhel).noarch.rpm<\/span><\/p><\/div>

    Loaded plugins: auto-update-debuginfo, fastestmirror<\/span><\/p><\/div>

    elevate-release-latest-el7.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 6.6 kB\u00a0\u00a0\u00a0\u00a0 00:00<\/span><\/p><\/div>

    Examining \/var\/tmp\/yum-root-nXSITp\/elevate-release-latest-el7.noarch.rpm: elevate-release-1.0-2.el7.noarch<\/span><\/p><\/div>

    Marking \/var\/tmp\/yum-root-nXSITp\/elevate-release-latest-el7.noarch.rpm to be installed<\/span><\/p><\/div>

    Resolving Dependencies<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package elevate-release.noarch 0:1.0-2.el7 will be installed<\/span><\/p><\/div>

    –> Finished Dependency Resolution<\/span><\/p><\/div>

    Dependencies Resolved<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    \u00a0Package\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Arch\u00a0\u00a0\u00a0 Version\u00a0\u00a0\u00a0\u00a0 Repository\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Size<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    Installing:<\/span><\/p><\/div>

    \u00a0elevate-release\u00a0 noarch\u00a0 1.0-2.el7\u00a0\u00a0 \/elevate-release-latest-el7.noarch\u00a0 3.4 k<\/span><\/p><\/div>

    Transaction Summary<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    Install\u00a0 1 Package<\/span><\/p><\/div>

    Total size: 3.4 k<\/span><\/p><\/div>

    Installed size: 3.4 k<\/span><\/p><\/div>

    Downloading packages:<\/span><\/p><\/div>

    Running transaction check<\/span><\/p><\/div>

    Running transaction test<\/span><\/p><\/div>

    Transaction test succeeded<\/span><\/p><\/div>

    Running transaction<\/span><\/p><\/div>

    \u00a0 Installing : elevate-release-1.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\/1<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : elevate-release-1.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\/1<\/span><\/p><\/div>

    Installed:<\/span><\/p><\/div>

    \u00a0 elevate-release.noarch 0:1.0-2.el7<\/span><\/p><\/div>

    Complete!<\/span><\/p><\/div><\/div>

    2. Install the LEAPP Package<\/h3>

    Specifically, we are going to install the leapp-data-rocky package, which will help us move to Rocky Linux, as opposed to AlmaLinux:<\/p>

    $ yum install -y leapp-upgrade leapp-data-rocky<\/span><\/p><\/div>

    Loaded plugins: auto-update-debuginfo, fastestmirror<\/span><\/p><\/div>

    Determining fastest mirrors<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    Resolving Dependencies<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package leapp-data-rocky.noarch 0:0.5-1.el7.20241127 will be installed<\/span><\/p><\/div>

    —> Package leapp-upgrade-el7toel8.noarch 1:0.21.0-4.el7.elevate.4 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: leapp-repository-dependencies = 10 for package: 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    –> Processing Dependency: leapp-framework >= 6.0 for package: 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    –> Processing Dependency: leapp for package: 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    –> Processing Dependency: python2-leapp for package: 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package leapp.noarch 0:0.18.0-2.el7 will be installed<\/span><\/p><\/div>

    —> Package leapp-upgrade-el7toel8-deps.noarch 1:0.21.0-4.el7.elevate.4 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: dnf >= 4 for package: 1:leapp-upgrade-el7toel8-deps-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    –> Processing Dependency: pciutils for package: 1:leapp-upgrade-el7toel8-deps-0.21.0-4.el7.elevate.4.noarch<\/span><\/p><\/div>

    —> Package python2-leapp.noarch 0:0.18.0-2.el7 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: leapp-framework-dependencies = 6 for package: python2-leapp-0.18.0-2.el7.noarch<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package dnf.noarch 0:4.0.9.2-2.el7_9 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: python2-dnf = 4.0.9.2-2.el7_9 for package: dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    —> Package leapp-deps.noarch 0:0.18.0-2.el7 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: PyYAML for package: leapp-deps-0.18.0-2.el7.noarch<\/span><\/p><\/div>

    —> Package pciutils.x86_64 0:3.5.1-3.el7 will be installed<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package PyYAML.x86_64 0:3.10-11.el7 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: libyaml-0.so.2()(64bit) for package: PyYAML-3.10-11.el7.x86_64<\/span><\/p><\/div>

    —> Package python2-dnf.noarch 0:4.0.9.2-2.el7_9 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: dnf-data = 4.0.9.2-2.el7_9 for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: python2-libdnf >= 0.22.5 for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: python2-libcomps >= 0.1.8 for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: python2-hawkey >= 0.22.5 for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: libmodulemd >= 1.4.0 for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: python2-libdnf for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Processing Dependency: deltarpm for package: python2-dnf-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package deltarpm.x86_64 0:3.6-3.el7 will be installed<\/span><\/p><\/div>

    —> Package dnf-data.noarch 0:4.0.9.2-2.el7_9 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: libreport-filesystem for package: dnf-data-4.0.9.2-2.el7_9.noarch<\/span><\/p><\/div>

    —> Package libmodulemd.x86_64 0:1.6.3-1.el7 will be installed<\/span><\/p><\/div>

    —> Package libyaml.x86_64 0:0.1.4-11.el7_0 will be installed<\/span><\/p><\/div>

    —> Package python2-hawkey.x86_64 0:0.22.5-2.el7_9 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: libdnf(x86-64) = 0.22.5-2.el7_9 for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libsolvext.so.0(SOLV_1.0)(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libsolv.so.0(SOLV_1.0)(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libsolvext.so.0()(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libsolv.so.0()(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: librepo.so.0()(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libdnf.so.2()(64bit) for package: python2-hawkey-0.22.5-2.el7_9.x86_64<\/span><\/p><\/div>

    —> Package python2-libcomps.x86_64 0:0.1.8-14.el7 will be installed<\/span><\/p><\/div>

    –> Processing Dependency: libcomps(x86-64) = 0.1.8-14.el7 for package: python2-libcomps-0.1.8-14.el7.x86_64<\/span><\/p><\/div>

    –> Processing Dependency: libcomps.so.0.1.6()(64bit) for package: python2-libcomps-0.1.8-14.el7.x86_64<\/span><\/p><\/div>

    —> Package python2-libdnf.x86_64 0:0.22.5-2.el7_9 will be installed<\/span><\/p><\/div>

    –> Running transaction check<\/span><\/p><\/div>

    —> Package libcomps.x86_64 0:0.1.8-14.el7 will be installed<\/span><\/p><\/div>

    —> Package libdnf.x86_64 0:0.22.5-2.el7_9 will be installed<\/span><\/p><\/div>

    —> Package librepo.x86_64 0:1.8.1-8.el7_9 will be installed<\/span><\/p><\/div>

    —> Package libreport-filesystem.x86_64 0:2.1.11-53.el7.centos will be installed<\/span><\/p><\/div>

    —> Package libsolv.x86_64 0:0.6.34-4.el7 will be installed<\/span><\/p><\/div>

    –> Finished Dependency Resolution<\/span><\/p><\/div>

    Dependencies Resolved<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    \u00a0Package\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Arch\u00a0\u00a0 Version\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Repository\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Size<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    Installing:<\/span><\/p><\/div>

    \u00a0leapp-data-rocky\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 0.5-1.el7.20241127\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 323 k<\/span><\/p><\/div>

    \u00a0leapp-upgrade-el7toel8 noarch 1:0.21.0-4.el7.elevate.4 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1.2 M<\/span><\/p><\/div>

    Installing for dependencies:<\/span><\/p><\/div>

    \u00a0PyYAML\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 3.10-11.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0 153 k<\/span><\/p><\/div>

    \u00a0deltarpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 3.6-3.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0\u00a0 82 k<\/span><\/p><\/div>

    \u00a0dnf\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 4.0.9.2-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0 357 k<\/span><\/p><\/div>

    \u00a0dnf-data\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 4.0.9.2-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0\u00a0 51 k<\/span><\/p><\/div>

    \u00a0leapp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 0.18.0-2.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 31 k<\/span><\/p><\/div>

    \u00a0leapp-deps\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 0.18.0-2.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13 k<\/span><\/p><\/div>

    \u00a0leapp-upgrade-el7toel8-deps<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 1:0.21.0-4.el7.elevate.4 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 41 k<\/span><\/p><\/div>

    \u00a0libcomps\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.1.8-14.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0\u00a0 75 k<\/span><\/p><\/div>

    \u00a0libdnf\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.22.5-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0 535 k<\/span><\/p><\/div>

    \u00a0libmodulemd\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 1.6.3-1.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0 141 k<\/span><\/p><\/div>

    \u00a0librepo\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 1.8.1-8.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-updates\u00a0 82 k<\/span><\/p><\/div>

    \u00a0libreport-filesystem\u00a0\u00a0 x86_64 2.1.11-53.el7.centos\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0\u00a0 41 k<\/span><\/p><\/div>

    \u00a0libsolv\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.6.34-4.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0 329 k<\/span><\/p><\/div>

    \u00a0libyaml\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.1.4-11.el7_0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0\u00a0 55 k<\/span><\/p><\/div>

    \u00a0pciutils\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 3.5.1-3.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-base\u00a0\u00a0\u00a0\u00a0 93 k<\/span><\/p><\/div>

    \u00a0python2-dnf\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 4.0.9.2-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0 414 k<\/span><\/p><\/div>

    \u00a0python2-hawkey\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.22.5-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0\u00a0 71 k<\/span><\/p><\/div>

    \u00a0python2-leapp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch 0.18.0-2.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 elevate\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 195 k<\/span><\/p><\/div>

    \u00a0python2-libcomps\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.1.8-14.el7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0\u00a0 47 k<\/span><\/p><\/div>

    \u00a0python2-libdnf\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x86_64 0.22.5-2.el7_9\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 C7.9.2009-extras\u00a0 611 k<\/span><\/p><\/div>

    Transaction Summary<\/span><\/p><\/div>

    ================================================================================<\/span><\/p><\/div>

    Install\u00a0 2 Packages (+20 Dependent packages)<\/span><\/p><\/div>

    Total download size: 4.8 M<\/span><\/p><\/div>

    Installed size: 33 M<\/span><\/p><\/div>

    Downloading packages:<\/span><\/p><\/div>

    (1\/22): deltarpm-3.6-3.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 82 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    warning: \/var\/cache\/yum\/x86_64\/7\/elevate\/packages\/leapp-0.18.0-2.el7.noarch.rpm: Header V4 RSA\/SHA256 Signature, key ID 81b961a5: NOKEY<\/span><\/p><\/div>

    Public key for leapp-0.18.0-2.el7.noarch.rpm is not installed<\/span><\/p><\/div>

    (2\/22): leapp-0.18.0-2.el7.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 31 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (3\/22): PyYAML-3.10-11.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 153 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (4\/22): leapp-deps-0.18.0-2.el7.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 13 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (5\/22): dnf-data-4.0.9.2-2.el7_9.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 51 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (6\/22): dnf-4.0.9.2-2.el7_9.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 357 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (7\/22): leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noar | 1.2 MB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (8\/22): leapp-upgrade-el7toel8-deps-0.21.0-4.el7.elevate.4 |\u00a0 41 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (9\/22): libcomps-0.1.8-14.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 75 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (10\/22): leapp-data-rocky-0.5-1.el7.20241127.noarch.rpm\u00a0\u00a0\u00a0 | 323 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (11\/22): libdnf-0.22.5-2.el7_9.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 535 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (12\/22): libmodulemd-1.6.3-1.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 141 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (13\/22): libreport-filesystem-2.1.11-53.el7.centos.x86_64. |\u00a0 41 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (14\/22): librepo-1.8.1-8.el7_9.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 82 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (15\/22): libyaml-0.1.4-11.el7_0.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 55 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (16\/22): pciutils-3.5.1-3.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 93 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (17\/22): python2-leapp-0.18.0-2.el7.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 195 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (18\/22): libsolv-0.6.34-4.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 329 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (19\/22): python2-hawkey-0.22.5-2.el7_9.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 71 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (20\/22): python2-libcomps-0.1.8-14.el7.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0 47 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (21\/22): python2-dnf-4.0.9.2-2.el7_9.noarch.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 414 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    (22\/22): python2-libdnf-0.22.5-2.el7_9.x86_64.rpm\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 611 kB\u00a0\u00a0 00:00<\/span><\/p><\/div>

    ——————————————————————————–<\/span><\/p><\/div>

    Total\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2.4 MB\/s | 4.8 MB\u00a0 00:01<\/span><\/p><\/div>

    Retrieving key from file:\/\/\/etc\/pki\/rpm-gpg\/RPM-GPG-KEY-ELevate<\/span><\/p><\/div>

    Importing GPG key 0x81B961A5:<\/span><\/p><\/div>

    \u00a0Userid\u00a0\u00a0\u00a0\u00a0 : “ELevate <packager@almalinux.org>”<\/span><\/p><\/div>

    \u00a0Fingerprint: 74e7 f249 ee69 8a4d acfb 48c8 4297 85e1 81b9 61a5<\/span><\/p><\/div>

    \u00a0Package\u00a0\u00a0\u00a0 : elevate-release-1.0-2.el7.noarch (@\/elevate-release-latest-el7.noarch)<\/span><\/p><\/div>

    \u00a0From\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : \/etc\/pki\/rpm-gpg\/RPM-GPG-KEY-ELevate<\/span><\/p><\/div>

    Running transaction check<\/span><\/p><\/div>

    Running transaction test<\/span><\/p><\/div>

    Transaction test succeeded<\/span><\/p><\/div>

    Running transaction<\/span><\/p><\/div>

    \u00a0 Installing : libsolv-0.6.34-4.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\/22<\/span><\/p><\/div>

    \u00a0 Installing : librepo-1.8.1-8.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2\/22<\/span><\/p><\/div>

    \u00a0 Installing : libyaml-0.1.4-11.el7_0.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 3\/22<\/span><\/p><\/div>

    \u00a0 Installing : libmodulemd-1.6.3-1.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 4\/22<\/span><\/p><\/div>

    \u00a0 Installing : libdnf-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\/22<\/span><\/p><\/div>

    \u00a0 Installing : python2-libdnf-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 6\/22<\/span><\/p><\/div>

    \u00a0 Installing : python2-hawkey-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 7\/22<\/span><\/p><\/div>

    \u00a0 Installing : PyYAML-3.10-11.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8\/22<\/span><\/p><\/div>

    \u00a0 Installing : leapp-deps-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 9\/22<\/span><\/p><\/div>

    \u00a0 Installing : python2-leapp-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 10\/22<\/span><\/p><\/div>

    \u00a0 Installing : pciutils-3.5.1-3.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 11\/22<\/span><\/p><\/div>

    \u00a0 Installing : deltarpm-3.6-3.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 12\/22<\/span><\/p><\/div>

    \u00a0 Installing : libreport-filesystem-2.1.11-53.el7.centos.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13\/22<\/span><\/p><\/div>

    \u00a0 Installing : dnf-data-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14\/22<\/span><\/p><\/div>

    \u00a0 Installing : libcomps-0.1.8-14.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 15\/22<\/span><\/p><\/div>

    \u00a0 Installing : python2-libcomps-0.1.8-14.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 16\/22<\/span><\/p><\/div>

    \u00a0 Installing : python2-dnf-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 17\/22<\/span><\/p><\/div>

    \u00a0 Installing : dnf-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 18\/22<\/span><\/p><\/div>

    \u00a0 Installing : 1:leapp-upgrade-el7toel8-deps-0.21.0-4.el7.elevate.4.noa\u00a0\u00a0 19\/22<\/span><\/p><\/div>

    \u00a0 Installing : leapp-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 20\/22<\/span><\/p><\/div>

    \u00a0 Installing : 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch\u00a0\u00a0\u00a0\u00a0 21\/22<\/span><\/p><\/div>

    \u00a0 Installing : leapp-data-rocky-0.5-1.el7.20241127.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 22\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : dnf-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : leapp-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libdnf-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 3\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : librepo-1.8.1-8.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 4\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libmodulemd-1.6.3-1.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : dnf-data-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 6\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : leapp-data-rocky-0.5-1.el7.20241127.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 7\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libcomps-0.1.8-14.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libreport-filesystem-2.1.11-53.el7.centos.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 9\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : python2-hawkey-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 10\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : deltarpm-3.6-3.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 11\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : python2-dnf-4.0.9.2-2.el7_9.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 12\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : leapp-deps-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : python2-libdnf-0.22.5-2.el7_9.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 14\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libyaml-0.1.4-11.el7_0.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 15\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : python2-libcomps-0.1.8-14.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 16\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : 1:leapp-upgrade-el7toel8-0.21.0-4.el7.elevate.4.noarch\u00a0\u00a0\u00a0\u00a0 17\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : 1:leapp-upgrade-el7toel8-deps-0.21.0-4.el7.elevate.4.noa\u00a0\u00a0 18\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : libsolv-0.6.34-4.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 19\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : python2-leapp-0.18.0-2.el7.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 20\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : PyYAML-3.10-11.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 21\/22<\/span><\/p><\/div>

    \u00a0 Verifying\u00a0 : pciutils-3.5.1-3.el7.x86_64\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 22\/22<\/span><\/p><\/div>

    Installed:<\/span><\/p><\/div>

    \u00a0 leapp-data-rocky.noarch 0:0.5-1.el7.20241127<\/span><\/p><\/div>

    \u00a0 leapp-upgrade-el7toel8.noarch 1:0.21.0-4.el7.elevate.4<\/span><\/p><\/div>

    Dependency Installed:<\/span><\/p><\/div>

    \u00a0 PyYAML.x86_64 0:3.10-11.el7<\/span><\/p><\/div>

    \u00a0 deltarpm.x86_64 0:3.6-3.el7<\/span><\/p><\/div>

    \u00a0 dnf.noarch 0:4.0.9.2-2.el7_9<\/span><\/p><\/div>

    \u00a0 dnf-data.noarch 0:4.0.9.2-2.el7_9<\/span><\/p><\/div>

    \u00a0 leapp.noarch 0:0.18.0-2.el7<\/span><\/p><\/div>

    \u00a0 leapp-deps.noarch 0:0.18.0-2.el7<\/span><\/p><\/div>

    \u00a0 leapp-upgrade-el7toel8-deps.noarch 1:0.21.0-4.el7.elevate.4<\/span><\/p><\/div>

    \u00a0 libcomps.x86_64 0:0.1.8-14.el7<\/span><\/p><\/div>

    \u00a0 libdnf.x86_64 0:0.22.5-2.el7_9<\/span><\/p><\/div>

    \u00a0 libmodulemd.x86_64 0:1.6.3-1.el7<\/span><\/p><\/div>

    \u00a0 librepo.x86_64 0:1.8.1-8.el7_9<\/span><\/p><\/div>

    \u00a0 libreport-filesystem.x86_64 0:2.1.11-53.el7.centos<\/span><\/p><\/div>

    \u00a0 libsolv.x86_64 0:0.6.34-4.el7<\/span><\/p><\/div>

    \u00a0 libyaml.x86_64 0:0.1.4-11.el7_0<\/span><\/p><\/div>

    \u00a0 pciutils.x86_64 0:3.5.1-3.el7<\/span><\/p><\/div>

    \u00a0 python2-dnf.noarch 0:4.0.9.2-2.el7_9<\/span><\/p><\/div>

    \u00a0 python2-hawkey.x86_64 0:0.22.5-2.el7_9<\/span><\/p><\/div>

    \u00a0 python2-leapp.noarch 0:0.18.0-2.el7<\/span><\/p><\/div>

    \u00a0 python2-libcomps.x86_64 0:0.1.8-14.el7<\/span><\/p><\/div>

    \u00a0 python2-libdnf.x86_64 0:0.22.5-2.el7_9<\/span><\/p><\/div>

    Complete!<\/span><\/p><\/div><\/div><\/div>

    3. Run the Pre-Upgrade Checks<\/h3>

    This stage is typically where sticky situations will show up. Even on a simple system like the one we’re using for this example, the pre-upgrade is very likely to have critical errors.<\/p>

    It is worth noting that this step does not change the system, so no side effects should be expected from running this command; notice that it does not require root permissions.<\/p>

    $ leapp preupgrade<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 REPORT OVERVIEW<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    Upgrade has been inhibited due to the following problems:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 1. Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed.<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 2. Missing required answers in the answer file<\/span><\/p><\/div>

    HIGH and MEDIUM severity reports:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 1. GRUB2 core will be automatically updated during the upgrade<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 2. Difference in Python versions and support in RHEL 8<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 3. Packages not signed by Red Hat found on the system<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 4. Detected custom leapp actors or files.<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 5. Detected customized configuration for dynamic linker.<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 6. ipa-server package is installed but no IdM is configured<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 7. chrony using default configuration<\/span><\/p><\/div>

    Reports summary:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 Errors:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 Inhibitors:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 HIGH severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 MEDIUM severity reports:\u00a0\u00a0\u00a0\u00a0 2<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 LOW severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 4<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 INFO severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2<\/span><\/p><\/div>

    Before continuing, review the full report below for details about discovered problems and possible remediation instructions:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 A report has been generated at \/var\/log\/leapp\/leapp-report.txt<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 A report has been generated at \/var\/log\/leapp\/leapp-report.json<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 END OF REPORT OVERVIEW<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    The leapp-report.txt that is generated from the pre-upgrade command contains some canned resolutions to the errors it generated. Let\u2019s try some of those answers!<\/p>

    # Remove pkcs11 module<\/span><\/p><\/div>

    $ leapp answer –section remove_pam_pkcs11_module_check.confirm=True<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    $ rmmod pata_acpi floppy<\/span><\/p><\/div>

    There are plenty of other messages that were generated and put in the report, but only the ones we used above were necessary for the upgrade to move forward. If you have third-party repositories, there\u2019s a possibility that upgraded versions of system dependencies might be present. You\u2019ll have to manually remove or downgrade those packages to resolve these version inconsistencies.<\/p>

    In order for the upgrade to proceed, you can\u2019t have any errors that will inhibit the upgrade. This will appear in the \u201cReports Summary\u201d under \u201cInhibitors.\u201d You may address some of the warnings that appear by examining the report and testing the suggestions they provide to see if you can resolve the warnings. Keep in mind only the inhibitors are required to proceed, though.<\/p>

    4. Run the Upgrade Process, Reboot, and Test<\/h3>

    $ leapp upgrade<\/span><\/p>

    Once this command completes, it\u2019s time to reboot into the new kernel. You will need to manually intervene and select the new boot option in GRUB: ELevate-Upgrade-<\/span>Initramfs<\/span><\/p>

    Now that you\u2019ve booted into the new environment, you should see that you\u2019re running on Rocky 8. Run through your standard QA tests to make sure the services the host is providing all work as expected. Continuing the upgrade to Rocky 9 isn\u2019t likely to fix services that are broken at this stage, so conduct a thorough check before continuing the upgrade.<\/p>

    5. Upgrade to Rocky 9<\/h3>

    The steps for continuing the upgrade to Rocky 9 are similar to the steps we took to upgrade to Rocky 8, starting with the ELevate repo:<\/p>

    $ yum install -y http:\/\/repo.almalinux.org\/elevate\/elevate-release-latest-el$(rpm<\/a> –eval %rhel).noarch.rpm<\/span><\/p>

    Next, we can remove package exclusions that were added from the previous LEAPP upgrade:<\/p>

    $ yum config-manager –save –setopt exclude=”<\/span><\/p>

    You might run into a scenario like we did where we had to remove LEAPP with its dependencies, because because leapp-upgrade-el7toel8 was still installed, and it failed because it didn’t match the version. Then you can install the following:<\/p>

    $ yum install -y leapp-upgrade leapp-data-rocky<\/span><\/p>

    And then run the LEAPP preupgrade again:
    $ leapp preupgrade<\/span><\/p>

    The output of the report will be similar to the previous one. After examining the report, we had to run these steps:<\/p>

    $ sed -i “s\/^AllowZoneDrifting=.*\/AllowZoneDrifting=no\/” \/etc\/<\/span>firewalld<\/span>\/<\/span>firewalld.conf<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    $ leapp answer –section check_vdo.confirm=True<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    Note: If root login is allowed, the report will fail. We resolved this by overriding our sshd_config:<\/p>

    $ sed -i ‘s\/^PermitRootLogin yes$\/PermitRootLogin yes # test\/’ \/etc\/ssh\/sshd_config<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    Here was our last report before we ran the upgrade again:<\/p>

    $ leapp upgrade<\/span><\/p><\/div>

    …<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 REPORT OVERVIEW<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    HIGH and MEDIUM severity reports:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 1. Packages not signed by Red Hat found on the system<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 2. Detected custom leapp actors or files.<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 3. Leapp detected loaded kernel drivers which are no longer maintained in RHEL 9.<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 4. Remote root logins globally allowed using password<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 5. GRUB2 core will be automatically updated during the upgrade<\/span><\/p><\/div>

    Reports summary:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 Errors:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 Inhibitors:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 HIGH severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 5<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 MEDIUM severity reports:\u00a0\u00a0\u00a0\u00a0 0<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 LOW severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 2<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 INFO severity reports:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 3<\/span><\/p><\/div>

    Before continuing, review the full report below for details about discovered problems and possible remediation instructions:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 A report has been generated at \/var\/log\/leapp\/leapp-report.txt<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 A report has been generated at \/var\/log\/leapp\/leapp-report.json<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 END OF REPORT OVERVIEW<\/span><\/p><\/div>

    ============================================================<\/span><\/p><\/div>

    Let\u2019s give it a shot!<\/p>

    $ leapp upgrade<\/span><\/p>

    Again, even on a simple system, we can get blocking errors:<\/p>

    Following errors occurred and the upgrade cannot continue:<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0 1. Actor: dnf_package_download<\/span><\/p><\/div>

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Message: DNF execution failed with non zero exit code.<\/span><\/p><\/div>

    Looking at \/var\/log\/leapp\/leapp-report.txt, there are a number of warnings, including a conflict between rocky-logos 86.3-1.el8 and rocky-logos-90.15-2.el9:<\/p>

    file \/usr\/share\/redhat-logos from install of rocky-logos-90.15-2.el9.x86_64 conflicts with file from package rocky-logos-86.3-1.el8.x86_64<\/span><\/p>

    To resolve this, we removed rocky-logos (which also removed rocky-backgrounds), and re-ran the LEAPP upgrade. Our next step was reboot, just as we did during the CentOS 7 to Rocky 8 upgrade, and select the grub entry ELevate-Upgrade-Initramfs again, and watch it go!<\/p>

    Upon rebooting, it was time to remove the excludes again:<\/p>

    $ yum config-manager –save –setopt exclude=”<\/span><\/p>

    Then we could remove orphaned packages, which cleans up the system and makes it more secure:<\/p>

    $ rpm -qa | grep -E ‘el8[.-]’ | xargs rpm -e<\/span><\/p>

    The same goes for the LEAPP packages, since they\u2019re not needed anymore:<\/p>

    $ dnf remove $(rpm -qa|grep leapp)<\/span><\/p>

    Done! Now it’s time to run our E2E and integration tests. After thorough testing of this host, it will be ready to re-enter production as an upgraded system.<\/p>

    Final Thoughts<\/h2>

    Organizations with a long list of hosts in their host inventory, or hosts with especially complex software inventories, may need assistance sorting out all of the complexities associated with a CentOS to Rocky Linux migration. Or they might need more time than they initially allotted for the project. Partnering with OpenLogic for CentOS long-term support <\/a>or migration services can ease the burden considerably. Our Professional Services team can help you plan your migration or provide hands-on-keyboard support throughout the process. And after you have successfully migrated, our Enterprise Architects can offer Rocky Linux support<\/a> up to 24-7.<\/p><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t
    \n\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t\t
    \n\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    About Perforce <\/strong>
    The best run DevOps teams in the world choose Perforce. Perforce products are purpose-built to develop, build and maintain high-stakes applications. Companies can finally manage complexity, achieve speed without compromise, improve security and compliance, and run their DevOps toolchains with full integrity. With a global footprint spanning more than 80 countries and including over 75% of the Fortune 100, Perforce is trusted by the world\u2019s leading brands to deliver solutions to even the toughest challenges. Accelerate technology delivery, with no shortcuts.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t\n\t\t

    \n\t\t\t\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t\t
    \n\t\t\t
    \n\t\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    About Version 2 Digital<\/h3>

    Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.\n

    \nThrough an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.<\/p><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

    On June 30, 2024, the ten-year run of CentOS 7 came to […]<\/p>\n","protected":false},"author":149011790,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1305,1298,61],"tags":[1077,1302],"class_list":["post-105498","post","type-post","status-publish","format-standard","hentry","category-1305","category-openlogic","category-press-release","tag-1077","tag-openlogic"],"acf":[],"yoast_head":"\nPlanning a CentOS to Rocky Linux Migration - Version 2<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration\" \/>\n<meta property=\"og:locale\" content=\"zh_HK\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Planning a CentOS to Rocky Linux Migration - Version 2\" \/>\n<meta property=\"og:description\" content=\"On June 30, 2024, the ten-year run of CentOS 7 came to […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration\" \/>\n<meta property=\"og:site_name\" content=\"Version 2\" \/>\n<meta property=\"article:published_time\" content=\"2025-03-12T04:09:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-03-24T04:40:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png\" \/>\n<meta name=\"author\" content=\"tracylamv2\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u4f5c\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"tracylamv2\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u9810\u8a08\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/2025\\\/03\\\/planning-a-centos-to-rocky-linux-migration\\\/\"},\"author\":{\"name\":\"tracylamv2\",\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#\\\/schema\\\/person\\\/011bc7c3731c930bcfeecd52fefb6365\"},\"headline\":\"Planning a CentOS to Rocky Linux Migration\",\"datePublished\":\"2025-03-12T04:09:04+00:00\",\"dateModified\":\"2025-03-24T04:40:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/2025\\\/03\\\/planning-a-centos-to-rocky-linux-migration\\\/\"},\"wordCount\":4639,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.openlogic.com\\\/sites\\\/default\\\/files\\\/image\\\/2022-08\\\/image-blog-openlogic-centos-to-rocky-migration-1.png\",\"keywords\":[\"2025\",\"OpenLogic\"],\"articleSection\":[\"2025\",\"Openlogic\",\"Press Release\"],\"inLanguage\":\"zh-HK\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/version-2.com\\\/2025\\\/03\\\/planning-a-centos-to-rocky-linux-migration\\\/\",\"url\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration\",\"name\":\"Planning a CentOS to Rocky Linux Migration - Version 2\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.openlogic.com\\\/sites\\\/default\\\/files\\\/image\\\/2022-08\\\/image-blog-openlogic-centos-to-rocky-migration-1.png\",\"datePublished\":\"2025-03-12T04:09:04+00:00\",\"dateModified\":\"2025-03-24T04:40:23+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#breadcrumb\"},\"inLanguage\":\"zh-HK\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-HK\",\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#primaryimage\",\"url\":\"https:\\\/\\\/www.openlogic.com\\\/sites\\\/default\\\/files\\\/image\\\/2022-08\\\/image-blog-openlogic-centos-to-rocky-migration-1.png\",\"contentUrl\":\"https:\\\/\\\/www.openlogic.com\\\/sites\\\/default\\\/files\\\/image\\\/2022-08\\\/image-blog-openlogic-centos-to-rocky-migration-1.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.openlogic.com\\\/blog\\\/planning-centos-rocky-linux-migration#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u9996\u9801\",\"item\":\"https:\\\/\\\/version-2.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Planning a CentOS to Rocky Linux Migration\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#website\",\"url\":\"https:\\\/\\\/version-2.com\\\/zh\\\/\",\"name\":\"Version 2\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/version-2.com\\\/zh\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-HK\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#organization\",\"name\":\"Version 2\",\"url\":\"https:\\\/\\\/version-2.com\\\/zh\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-HK\",\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/version-2.com\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/v2-hk-hor-4.png?fit=1795%2C335&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/version-2.com\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/v2-hk-hor-4.png?fit=1795%2C335&ssl=1\",\"width\":1795,\"height\":335,\"caption\":\"Version 2\"},\"image\":{\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/version-2.com\\\/zh\\\/#\\\/schema\\\/person\\\/011bc7c3731c930bcfeecd52fefb6365\",\"name\":\"tracylamv2\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-HK\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g\",\"caption\":\"tracylamv2\"},\"url\":\"https:\\\/\\\/version-2.com\\\/zh\\\/author\\\/tracylamv2\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Planning a CentOS to Rocky Linux Migration - Version 2","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration","og_locale":"zh_HK","og_type":"article","og_title":"Planning a CentOS to Rocky Linux Migration - Version 2","og_description":"On June 30, 2024, the ten-year run of CentOS 7 came to […]","og_url":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration","og_site_name":"Version 2","article_published_time":"2025-03-12T04:09:04+00:00","article_modified_time":"2025-03-24T04:40:23+00:00","og_image":[{"url":"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png","type":"","width":"","height":""}],"author":"tracylamv2","twitter_card":"summary_large_image","twitter_misc":{"\u4f5c\u8005":"tracylamv2","\u9810\u8a08\u95b1\u8b80\u6642\u9593":"19 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#article","isPartOf":{"@id":"https:\/\/version-2.com\/2025\/03\/planning-a-centos-to-rocky-linux-migration\/"},"author":{"name":"tracylamv2","@id":"https:\/\/version-2.com\/zh\/#\/schema\/person\/011bc7c3731c930bcfeecd52fefb6365"},"headline":"Planning a CentOS to Rocky Linux Migration","datePublished":"2025-03-12T04:09:04+00:00","dateModified":"2025-03-24T04:40:23+00:00","mainEntityOfPage":{"@id":"https:\/\/version-2.com\/2025\/03\/planning-a-centos-to-rocky-linux-migration\/"},"wordCount":4639,"commentCount":0,"publisher":{"@id":"https:\/\/version-2.com\/zh\/#organization"},"image":{"@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#primaryimage"},"thumbnailUrl":"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png","keywords":["2025","OpenLogic"],"articleSection":["2025","Openlogic","Press Release"],"inLanguage":"zh-HK","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#respond"]}]},{"@type":"WebPage","@id":"https:\/\/version-2.com\/2025\/03\/planning-a-centos-to-rocky-linux-migration\/","url":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration","name":"Planning a CentOS to Rocky Linux Migration - Version 2","isPartOf":{"@id":"https:\/\/version-2.com\/zh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#primaryimage"},"image":{"@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#primaryimage"},"thumbnailUrl":"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png","datePublished":"2025-03-12T04:09:04+00:00","dateModified":"2025-03-24T04:40:23+00:00","breadcrumb":{"@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#breadcrumb"},"inLanguage":"zh-HK","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration"]}]},{"@type":"ImageObject","inLanguage":"zh-HK","@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#primaryimage","url":"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png","contentUrl":"https:\/\/www.openlogic.com\/sites\/default\/files\/image\/2022-08\/image-blog-openlogic-centos-to-rocky-migration-1.png"},{"@type":"BreadcrumbList","@id":"https:\/\/www.openlogic.com\/blog\/planning-centos-rocky-linux-migration#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u9996\u9801","item":"https:\/\/version-2.com\/"},{"@type":"ListItem","position":2,"name":"Planning a CentOS to Rocky Linux Migration"}]},{"@type":"WebSite","@id":"https:\/\/version-2.com\/zh\/#website","url":"https:\/\/version-2.com\/zh\/","name":"Version 2","description":"","publisher":{"@id":"https:\/\/version-2.com\/zh\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/version-2.com\/zh\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-HK"},{"@type":"Organization","@id":"https:\/\/version-2.com\/zh\/#organization","name":"Version 2","url":"https:\/\/version-2.com\/zh\/","logo":{"@type":"ImageObject","inLanguage":"zh-HK","@id":"https:\/\/version-2.com\/zh\/#\/schema\/logo\/image\/","url":"https:\/\/i0.wp.com\/version-2.com\/wp-content\/uploads\/2020\/08\/v2-hk-hor-4.png?fit=1795%2C335&ssl=1","contentUrl":"https:\/\/i0.wp.com\/version-2.com\/wp-content\/uploads\/2020\/08\/v2-hk-hor-4.png?fit=1795%2C335&ssl=1","width":1795,"height":335,"caption":"Version 2"},"image":{"@id":"https:\/\/version-2.com\/zh\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/version-2.com\/zh\/#\/schema\/person\/011bc7c3731c930bcfeecd52fefb6365","name":"tracylamv2","image":{"@type":"ImageObject","inLanguage":"zh-HK","@id":"https:\/\/secure.gravatar.com\/avatar\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9d01d79cbfd8b2e878f5d701a362cc9fca466d33fec977b59706c23c1a2db15c?s=96&d=identicon&r=g","caption":"tracylamv2"},"url":"https:\/\/version-2.com\/zh\/author\/tracylamv2\/"}]}},"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pbQRKm-rrA","post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/posts\/105498","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/users\/149011790"}],"replies":[{"embeddable":true,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/comments?post=105498"}],"version-history":[{"count":9,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/posts\/105498\/revisions"}],"predecessor-version":[{"id":108711,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/posts\/105498\/revisions\/108711"}],"wp:attachment":[{"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/media?parent=105498"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/categories?post=105498"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/version-2.com\/zh\/wp-json\/wp\/v2\/tags?post=105498"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}