Problem statement

Feedback from architects at the RHEL Conversions and Upgrades Feedback Workshop at 2025 Red Hat One revealed that:

The scope of what a LEAPP upgrade affects on a system differs from the expectations of the users.

Customers have an expectation that if a package (e.g. postgres) is unsupported on RHEL X then the LEAPP tool will upgrade them from an unsupported to a supported version of postgres on RHEL X+1.

See more at https://docs.google.com/presentation/d/1fCi0LvtnyiMAhRCcP9tqYNSJPLBs9IGWtkUXMjnZ4iE/edit#slide=id.g33a828d4ca5_0_86. 

Goal

As a leapp user,

I want the pre-upgrade analysis to tell me what is going to happen during the upgrade to packages I have installed on my system,

so that I have a clear picture of what software version will I have after the upgrade and whether it will be supported because right now I find that out only after performing the system upgrade itself.

Example

I run PostgreSQL 10 on RHEL 8 which went out of support in May 2024 (https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle). What version of postgres will I have after the upgrade to RHEL 9? There are versions 13, 15, and 16 available, with different years of retirement.

Or similarly, I run postgresql 15 on RHEL 8. Does leapp enable the non-default RHEL 9 postgresql 15 module stream during the upgrade so that I would run the same postgresql version even after the upgrade? Or does it downgrade to the non-modular postgresql 13, or rather the opposite, i.e. update to the latest modular version postgres 16?

Acceptance criteria

• The upgrade dnf plugin is enhanced in a way that it collects data from dnf about what's going to happen with installed packages
• The information from the plugin is then messaged to the user in the pre-upgrade report
  • Such a message could be huge if it includes all the installed packages  (1000s of lines) so one of the options is to point to a file generated by leapp so those interested could inspect the file.