Partially the problem is described in the commit msg here:

• https://github.com/oamg/leapp-repository/commit/cd7a8c29dba0b3273eb057b63957eb2d363e77a6

To summarize it, we have currently 2 places defining information about supported upgrade paths:

• shared configs.version library
• files/upgrade_paths.json

The first one is used to determine whether the current system is actually allowed to be upgraded with the installed leapp-upgrade* rpms. The other one is used to check where the system is allowed to be upgraded. Note that both these places must be synchronized all the time so the information in one is not in conflict with the other.

We need to unify the solution so we have one source of truth to read the enabled upgrade paths. The problem is that we do not want to access the upgrade_paths.json file again all the time to be able to access this information as e.g. we are clear that during the checksphase actors should not interact with the system. At this point, the information should be provided to actors either via messages or the IPUConfig. The current workaround we implemented uses the IPUPaths msg (already marked as deprecated so nobody depends on it by mistake) - - which I am not sure it's the right way, but can be considered to be used as well.

Also, starting with upgrades on CentOS Stream, we need to include the information also based on the distribution we are upgrading. Considering the solution should be more generic, so it should be simple in future to extend it by other distributions as well if wanted - so the format will not need to be changed. So part of this task is to examine what would be the best approach when we want to cover distro specific upgrade paths as well.

AC:

• there is only one place per distribution to get information about valid upgrade paths
• it could be just a one place at all (I would prefer that), but in case of need, we can consider one file per distribution under the distro directory
• the upgrade paths for RHEL and CS are specified