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

6.10 to 6.11 upgrade leaves python3-* packages on the system, which confuses Leapp and other tools

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 6.11.5
    • Upgrades
    • False
    • Moderate
    • Sat_docs_3_2023, Sat_docs_4_2023, Sat_docs_5_2023, Sat_docs_6_2023, Sat_docs_7_2023
    • None
    • None
    • None
    • None

      Document URL:
      https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/upgrading_and_updating_red_hat_satellite/index#upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide

      Section Number and Name:
      Chapter 4
      Chapter 4. Upgrading Satellite or Capsule to Red Hat Enterprise Linux 8 In-Place Using Leapp

      Describe the issue:
      After the leapp upgrade additional repositories not required by the Satellite could be enabled.

      Suggestions for improvement:
      One of the last steps for the leapp upgrade should be to run `satellite-maintain advanced procedure run repositories-setup --version 6.11` to disable all repositories and enable only the supported Satellite repositories.

      Additional information:
      After completing an upgrade the rhel-8-for-x86_64-highavailability-rpms has been seen as enabled. This repository is not needed for the Satellite. The command `satellite-maintain advanced procedure run repositories-setup --version 6.11` will disable all repositories on the Satellite and enable only the ones required for Satellite. This may not apply to disconnected Satellites as those repository labels could be different.

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: