Bug 2174590 - 6.10 to 6.11 upgrade leaves python3-* packages on the system, which confuses Leapp and other tools
Summary: 6.10 to 6.11 upgrade leaves python3-* packages on the system, which confuses ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infrastructure
Version: 6.11.5
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-01 22:22 UTC by Taft Sanders
Modified: 2023-07-07 00:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16230 0 None None None 2023-03-01 22:22:47 UTC

Description Taft Sanders 2023-03-01 22:22:09 UTC
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.

Comment 1 Marie Hornickova 2023-03-02 09:18:21 UTC
Hello Taft,
Many thanks for reporting the issue. 
The BZ is now assigned and the documentation team will shared detailed updates in the corresponding Jira.
Final link to fixed docs will be shared also here.
Thank you!


Note You need to log in before you can comment on or make changes to this bug.