This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2283067 - [Bug] - Leapp upgrade of Red Hat Satellite server failed with error tomcatjss-7.2.5-1.el7.noarch from @System does not belong to a distupgrade repository
Summary: [Bug] - Leapp upgrade of Red Hat Satellite server failed with error tomcatjss...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.11.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Evgeni Golov
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-23 21:46 UTC by Dhaval Joshi
Modified: 2024-06-27 11:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:40:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25331 0 None Migrated None 2024-06-27 11:44:28 UTC
Red Hat Knowledge Base (Solution) 7072410 0 None None None 2024-05-28 13:22:20 UTC

Description Dhaval Joshi 2024-05-23 21:46:40 UTC 
Description of problem:

Unable to perform RHEL-7 to RHEL-8 upgrade of Satellite server.
Upgrade path: RHEL 7.9 to RHEL 8.10

Version-Release number of selected component (if applicable):
Satellite 6.11.5

# rpm -qa | grep -i satellite
satellite-cli-6.11.5.7-1.el7sat.noarch
satellite-common-6.11.5.7-1.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch
satellite-6.11.5.7-1.el7sat.noarch
satellite-installer-6.11.0.7-1.el7sat.noarch

# rpm -qa | grep -i leapp
leapp-upgrade-el7toel8-deps-0.20.0-2.el7_9.noarch
leapp-0.17.0-1.el7_9.noarch
tfm-rubygem-foreman_leapp-0.1.9-1.el7sat.noarch
python2-leapp-0.17.0-1.el7_9.noarch
leapp-deps-0.17.0-1.el7_9.noarch
leapp-upgrade-el7toel8-0.20.0-2.el7_9.noarch


How reproducible:
100%

Steps to Reproduce:
1. Deploy Red Hat Satellite 6.11 on RHEL-7.
2. Update to 6.11.z.
3. Install required leapp packages.
4. Run preupgrade command
#leapp preupgrade

Actual results:
2024-05-23 17:32:40.323176 [ERROR] Actor: dnf_transaction_check
Message: DNF execution failed with non zero exit code.
Summary:
    Stdout: Last metadata expiration check: 0:01:40 ago on Thu May 23 17:30:47 2024.
            Package foreman-installer-katello-1:3.1.2.8-1.el7sat.noarch is already installed.
            Package rubygem-foreman_maintain-1:1.0.19-1.el7sat.noarch is already installed.
            Package tfm-rubygem-smart_proxy_ansible-3.3.1-5.el7sat.noarch is already installed.
            Package satellite-installer-6.11.0.7-1.el7sat.noarch is already installed.
            Package katello-4.3.0-3.el7sat.noarch is already installed.
            Package satellite-6.11.5.7-1.el7sat.noarch is already installed.
            Package foreman-installer-1:3.1.2.8-1.el7sat.noarch is already installed.
    Stderr: Warning: Package marked by Leapp to install not found in repositories metadata: log4j12
            Warning: Package marked by Leapp to upgrade not found in repositories metadata: python2-leapp leapp gpg-pubkey leapp-upgrade-el7toel8
            Transaction check: 
            
             Problem: problem with installed package tomcatjss-7.2.5-1.el7.noarch
              - cannot install the best update candidate for package tomcatjss-7.2.5-1.el7.noarch
              - package idm-tomcatjss-7.8.0-1.module+el8.10.0+21280+cce842b8.noarch from rhel-8-for-x86_64-appstream-rpms requires tomcat, but none of the providers can be installed
              - tomcatjss-7.2.5-1.el7.noarch from @System  does not belong to a distupgrade repository
              - conflicting requests
    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.

============================================================
                       END OF ERRORS                        
============================================================

Debug output written to /var/log/leapp/leapp-preupgrade.log

============================================================
                      REPORT OVERVIEW                       
============================================================

Following errors occurred and the upgrade cannot continue:
    1. Actor: dnf_transaction_check
       Message: DNF execution failed with non zero exit code.

HIGH and MEDIUM severity reports:
    1. Packages available in excluded repositories will not be installed
    2. Difference in Python versions and support in RHEL 8
    3. GRUB2 core will be automatically updated during the upgrade
    4. Module pam_pkcs11 will be removed from PAM configuration
    5. chrony using default configuration
    6. Satellite PostgreSQL data migration

Reports summary:
    Errors:                      1
    Inhibitors:                  0
    HIGH severity reports:       3
    MEDIUM severity reports:     3
    LOW severity reports:        6
    INFO severity reports:       4

Before continuing consult the full report:
    A report has been generated at /var/log/leapp/leapp-report.json
    A report has been generated at /var/log/leapp/leapp-report.txt


Expected results:
 - Upgrade should be successful without any issues.

Additional info:
 - leapp preupgrade --target 8.8 worked when we skipped the below steps from the documentation.
# echo tomcat >> /etc/leapp/transaction/to_remove
# echo tomcat-lib >> /etc/leapp/transaction/to_remove
Comment 4 Evgeni Golov 2024-05-27 10:31:04 UTC 
Workaround:
Edit the file /etc/leapp/repos.d/system_upgrade/el7toel8/actors/satellite_upgrade_facts/actor.py
Remove the "to_remove.extend(['tomcat', 'tomcat-lib'])" line (line 62).
Comment 5 Evgeni Golov 2024-05-27 10:47:59 UTC 
Better workaround:
Add "tomcat" and "tomcat-lib" to /etc/leapp/transaction/to_keep (and not add them to to_remove)
Comment 6 Evgeni Golov 2024-05-27 11:39:18 UTC 
The docs have been updated to reflect this.
Not sure we'll get the change into leapp quickly enough, but at least it's now correctly documented.
Comment 12 Eric Helms 2024-06-06 17:40:10 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.