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

7.9 to 8.10 RHUI SAP upgrade broken due to renamed client rhui rpms [AWS]

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhel-7.9.z
    • rhel-7.9.z
    • leapp-repository
    • None
    • None
    • Important
    • 1
    • rhel-sst-upgrades
    • 26
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Leapp: 9.5 & 10.0 public beta
    • Unspecified
    • None

      What were you trying to do that didn't work?

      RHEL major version upgrade from RHEL 7.9 to RHEL 8.10 on AWS using RHUI as source does not work.

      Please provide the package NVR for which bug is seen:

      leapp-0.17.0-1.el7_9
      leapp-repository-0.20.0-2.el7_9

      How reproducible:

      Always

      Steps to reproduce

      1. Provision RHEL for SAP 7.9 in AWS
      2. Run leapp upgrade to 8.10 using RHUI

      Expected results

      Upgrade works

      Actual results

      Upgrade fails

      The issue is rhui client packages were renamed between 8.8 and 8.10:

      • 8.10, rh-amazon-rhui-client-sap-bundle-4.0.17-1.el8.noarch.rpm:
        • /etc/pki/rhui/content-rhel8-sap-bundle.key
        • /etc/pki/rhui/product/content-rhel8-sap-bundle.crt
        • /etc/yum.repos.d/redhat-rhui-client-config-sap-bundle.repo
        • /etc/yum.repos.d/redhat-rhui-sap-bundle.repo
      • 8.8, rh-amazon-rhui-client-sap-bundle-e4s-4.0.17-1.el8.noarch.rpm:
        • /etc/pki/rhui/content-rhel8-sap-bundle-e4s.key
        • /etc/pki/rhui/product/content-rhel8-sap-bundle-e4s.crt
        • /etc/yum.repos.d/redhat-rhui-client-config-sap-bundle.repo <= it’s the same!
        • /etc/yum.repos.d/redhat-rhui-sap-bundle-e4s.repo

              leapp-notifications leapp-notifications
              rhn-support-mkluson Martin Kluson
              leapp-notifications leapp-notifications
              RHEL Upgrades QE Team RHEL Upgrades QE Team
              Miriam Portman Miriam Portman
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: