Description of problem: During leapp pre-upgrade satellite-related repository is unknown to leapp. i.e rhel-7-server-satellite-tools-6.9-rpms rhel-server-rhscl-7-rpms Version-Release number of selected component (if applicable): RHEL 7.9 How reproducible: 100% Steps to Reproduce: 1. Make a fresh RHEL 7.9 system. 2. Register it with the Satellite server and enable basic repositories. 3. Enable the below-mentioned repositories. [1] rhel-7-server-satellite-tools-6.9-rpms [2] rhel-server-rhscl-7-rpms Actual results: Based on packages that are installed and coming from these repositories the following message appears in /var/log/leapp/leapp-report.txt ~~~ Title: Some enabled RPM repositories are unknown to Leapp Summary: The following repositories with Red Hat-signed packages are unknown to Leapp: - rhel-7-server-satellite-tools-6.9-rpms - rhel-server-rhscl-7-rpms And the following packages installed from those repositories may not be upgraded: ... ...{Package List} ... Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ~~~ Expected results: If these repositories are enabled then it should not appear in the report. Additional info:
I expected to for the RedHat promoted Satellite products also all client tools (e.g. puppet-agent) are updated. Currently after the leapp upgrade and using the correct sat6-tools-el8 repo there is still a el7sat rpm installed. This is easily spotted with doing a 'rpm -qa | grep el7' I expected that RedHat has already identified this missed upgrade and include them in the el7->el8 process. In case of puppet-agent it is a version number inconsistency and I have created already a dedicated case for the Satellite product for this