Description of problem: run leapp preupgrade with resilient storage channel is enabled and packages are installed will lead to: Risk Factor: low Title: Some enabled RPM repositories are unknown to Leapp Summary: The following repositories with Red Hat-signed packages are unknown to Leapp: - rhel-8-for-x86_64-resilientstorage-rpms And the following packages installed from those repositories may not be upgraded: - dlm - [SNIP] Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket Key: 8e89e20c645cea600b240156071d81c64daab7ad Version-Release number of selected component (if applicable): 0.18.0-1.el8_8.2 How reproducible: always Steps to Reproduce: 1. on any rhel8.8 machine 2. subscription-manager repos --enable rhel-8-for-x86_64-resilientstorage-rpms 2. yum install dlm 3. leapp preupgrade Actual results: as above, we get an error and the equivalent channel for rhel-9 is not enabled. Expected results: rhel-9-for-x86_64-resilientstorage-rpms enabled and used for the upgrade. Additional info: I have temporary worked around the problem by editing /etc/leapp/files/repomap.json and once resiliatstorage is enabled, it works like a champ :)
Hi, thank you for the report. It will be discussed for teams working on resilient storage. There is no need to update repomap.json for the workaround, it's possible to just apply the use of the repository manually when running leapp, in this case e.g.: # leapp upgrade --enablerepo rhel-9-for-x86_64-resilientstorage-rpms
(In reply to Petr Stodulka from comment #1) > Hi, thank you for the report. It will be discussed for teams working on > resilient storage. > There is no need to update repomap.json for the workaround, it's possible to > just apply the use of the repository manually when running leapp, in this > case e.g.: > # leapp upgrade --enablerepo rhel-9-for-x86_64-resilientstorage-rpms I see the difference with the command I used. I set --enablerepo with the rhel-8-* version and not 9. Tho it would be still nice to see it incorporated and less manual mingling from the end user.