Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-35409

Leapp upgrade with two results with the different custom repos, but these repos all from RHEL 9.4 iso.

XMLWordPrintable

    • False
    • None
    • None
    • None
    • None

      Description of problem:
      In my lab: Satellite 6.17, Create two products, and every product has two custom repos(AppStream, BaseOS). These repos all from RHEL 9.4 ISO(rhel-9.4-x86_64-dvd.iso), which was downloaded from the Red Hat Customer Portal.

      The first custom product: Custom_repo_1_upload
      The second custom product: Custom_repo_2_sync
       
      If I use the first product's repo to upgrade the system from RHEL 8 to RHEL 9.4 on client, it will hit the following error.
      ```
      Risk Factor: high (inhibitor)
      Title: Cannot find required basic RHEL target repositories.
      Summary: This can happen when a repository ID was entered incorrectly either while using the --enablerepo option of leapp or in a third party actor that produces a CustomTargetRepositoryMessage.
      Related links:

      • RHEL 7 to RHEL 8 LEAPP Upgrade Failing When Using Red Hat Satellite: https://access.redhat.com/solutions/5392811
      • Preparing for the upgrade: https://red.ht/preparing-for-upgrade-to-rhel9
        Remediation: [hint] It is required to have RHEL repositories on the system provided by the subscription-manager unless the --no-rhsm option is specified. You might be missing a valid SKU for the target system or have a failed network connection. Check whether your system is attached to a valid SKU that is providing RHEL 9 repositories. If you are using Red Hat Satellite, read the upgrade documentation to set up Satellite and the system properly.
        ```
        If I use the second product's repo to upgrade the system from RHEL 8 to RHEL 9.4 on the client, it will upgrade successfully.

      How reproducible:
      Prepare:

      • satellite server 6.17 & client 8.10

      Steps:
      1. On the Satellite UI creates two products, and then creates two repos(AppStream, BaseOS).

      • The first custom product: Custom_repo_1_upload (these two repos' content packages through the upload way. Please use the command to upload these packages, because the UI seems to have a bug if you upload too many packages at the same time. SAT-35291)
      • The second custom product: Custom_repo_2_sync (these two repos' content packages through the sync way. Configure the upstream URL to sync the http repo.)

      2. Create two content views for upgrading the RHEL8 client.

      3. Execute the following command for upgrading:
      ```

      1. leapp preupgrade --enablerepo Custom_repos_name_1 --enablerepo Custom_repos_name_1
        ```

      Is this issue a regression from an earlier version:

       

      Actual behavior:
      [Describe the issue in detail, including what is happening and where]
      Even if the repos' sources are the same from 'rhel-9.4-x86_64-dvd.iso', but if the custom repo is created in different ways, the leapp results are different.

      One is normal, One is with the following error:
      ```
      Risk Factor: high (inhibitor)
      Title: Cannot find required basic RHEL target repositories.
      Summary: This can happen when a repository ID was entered incorrectly either while using the --enablerepo option of leapp or in a third party actor that produces a CustomTargetRepositoryMessage.
      Related links:

      • RHEL 7 to RHEL 8 LEAPP Upgrade Failing When Using Red Hat Satellite: https://access.redhat.com/solutions/5392811
      • Preparing for the upgrade: https://red.ht/preparing-for-upgrade-to-rhel9
        Remediation: [hint] It is required to have RHEL repositories on the system provided by the subscription-manager unless the --no-rhsm option is specified. You might be missing a valid SKU for the target system or have a failed network connection. Check whether your system is attached to a valid SKU that is providing RHEL 9 repositories. If you are using Red Hat Satellite, read the upgrade documentation to set up Satellite and the system properly.
        ```

      Expected behavior:
      [Describe what should be happening instead]
      They all run normally.
      Business Impact / Additional info:

       

              Unassigned Unassigned
              rhn-support-jiahli Jiahui Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: