Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-21779

Leapp upgrade is failing with tomcatjss dependency issue

    • leapp-repository-0.19.0-10.el8
    • None
    • None
    • rhel-sst-upgrades
    • ssg_idm
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Pass
    • None
    • None

      Leapp Upgrade for 8.10 to 9.4 is failing where ipa-server packages are installed.

      2024-01-15T08:28:07+0000 2024-01-15 03:28:06.685525 [ERROR] Actor: dnf_transaction_check
      2024-01-15T08:28:07+0000 Message: DNF execution failed with non zero exit code.
      2024-01-15T08:28:07+0000 Summary:
      2024-01-15T08:28:07+0000 Stdout: Last metadata expiration check: 0:00:23 ago on Mon Jan 15 03:27:41 2024.
      2024-01-15T08:28:07+0000 Stderr: warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.
      2024-01-15T08:28:07+0000 No matches found for the following disable plugin patterns: subscription-manager
      2024-01-15T08:28:07+0000 warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend.
      2024-01-15T08:28:07+0000 Warning: Package marked by Leapp to install not found in repositories metadata: jaxb-impl pki-resteasy-jaxb-provider
      2024-01-15T08:28:07+0000 Warning: Package marked by Leapp to upgrade not found in repositories metadata: leapp-upgrade-el8toel9 leapp python3-leapp
      2024-01-15T08:28:07+0000 Transaction check:
      2024-01-15T08:28:07+0000
      2024-01-15T08:28:07+0000 Problem: conflicting requests
      2024-01-15T08:28:07+0000 - nothing provides jss = 5.4 needed by idm-tomcatjss-8.4.0-1.el9.noarch from rhel-9.4-AppStream
      2024-01-15T08:28:07+0000 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.
      2024-01-15T08:28:07+0000

              leapp-notifications leapp-notifications
              rhn-support-amore Anuja More
              leapp-notifications leapp-notifications
              Anuja More Anuja More
              Miriam Portman Miriam Portman
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: