CentOS 7 to AlmaLinux 8 - missing package checks for nodejs

[lucamosca1]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Environment
AWS EC2 CentOS 7 - Tentative upgrade to AlmaLinux and Rocky 8

Issue:
Preupgrade phase detected some issues such as a package that cannot be updated like javapackages-tools so that I have to remove it in order to proceed with update. After that preupgrade phase passed, upgrade phase passed also, but reboot/upgrade make my instance stuck. I forced a reboot and I booted again CentOS 7.

In /var/log/leapp/leapp-report.txt I found an other issue with pagages didn't found before:

Summary: {"hint": "If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process.", "STDERR": "No matches found for the following disable plugin patterns: subscription-manager\nRepository extras is listed more than once in the configuration\nWarning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp leapp-upgrade-el7toel8 python2-leapp\nTransaction couldn't start:\nfile /usr/lib/node_modules/npm/docs from install of npm-1:6.14.11-1.10.24.0.1.module+el8.3.0+101+f84c7154.x86_64 conflicts with file from package nodejs-2:10.24.1-1nodesource.x86_64\nError: Could not run transaction.\n", "STDOUT": "Last metadata expiration check: 0:12:37 ago on Thu Feb 27 13:02:25 2025.\nDependencies resolved.

So I had to remove also nodejs stuff with
sudo yum remove nodejs-10.24.1-1nodesource.x86_64
sudo yum remove nodesource-release-el7-1.noarch

After that, preupgrade, upgrade and reboot upgrade are ok. Is it possible to include this check in preupgrade phase to avoid the recover of a stuck system?

Expected Behavior

No response

Steps To Reproduce

No response

Anything else?

No response

Search terms

upgrade nodejs critical blocker

[yuravk]

@lucamosca1 , thanks for your report.

The issue can't be considered as bug, as you are using unsupported by ELevate repository/Vendor to install nodejs packages.

For now, to solve the issue you may:

• remove all nodejs related packages which block ELevation (as you did), and install them back after upgrade;
• contribute to the project with adding new nodejs vendor. Please find more on how to do that at https://wiki.almalinux.org/elevate/Contribution-guide.html#third-party-vendors-support