We need to make it more clear that Satellite requires the satellite-6.11-for-rhel-8-x86_64-rpms AND capsule requires the capsule variant of that repo. At this time, it's not clear at all that a Capsule needs this repo in its content view and/or sync'd on the Satellite. Reported by: rhn-support-jcastran https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/upgrading_and_updating_red_hat_satellite/upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide#annotations:85ec8274-f7db-4500-950c-46941dc86bbe
Reviewing this documentation a little further. i would like to request if i can piggy back on this ticket, that we actually seperate the connected vs the disconnected steps. Right now they "intermingle" in the doc and customers often follow a mix of the steps resulting in bad configurations. We should have ============================================================================== > Initial Steps Configure the repositories to obtain Leapp. On Red Hat Enterprise Linux, enable the rhel-7-server-extras-rpms repository: # subscription-manager repos --enable=rhel-7-server-extras-rpms Install required packages: # satellite-maintain packages install leapp leapp-repository ============================================================================== > CONNECTED Satellite and Capsule steps - Special prereq for capsule for what repos they need sync'd on the satellite and in their content view if applicable # leapp preupgrade The first run is expected to fail but report issues and inhibit the upgrade. Examine the report in the /var/log/leapp/leapp-report.txt file, answer all questions (using leapp answer), and manually resolve the other reported problems. The following commands show the most common steps required: # rmmod pata_acpi # echo PermitRootLogin yes | tee -a /etc/ssh/sshd_config # leapp answer --section remove_pam_pkcs11_module_check.confirm=True If leapp preupgrade inhibits the upgrade with Unsupported network configuration because there are multiple legacy named network interfaces, follow the instructions shown by Leapp to rename the interfaces, followed by an installer run to reconfigure Satellite or Capsule to use the new interface names: # satellite-installer --help |grep 'interface.*eth' --foreman-proxy-dhcp-interface DHCP listen interface (current: "eth0") --foreman-proxy-dns-interface DNS interface (current: "eth0") If eth0 was renamed to em0, call the installer to use the new interface name with: # satellite-installer --foreman-proxy-dhcp-interface=em0 --foreman-proxy-dns-interface=em0 # leapp upgrade ============================================================================== > DISCONNECTED Satellite and Capsule steps For Leapp to perform the upgrade in a disconnected environment, download the metadata and manually extract, as described in Leapp utility metadata in-place upgrades of RHEL for disconnected upgrades. Set up the following repositories to perform the upgrade in a disconnected environment: /etc/yum.repos.d/rhel8.repo: [BaseOS] name=rhel-8-for-x86_64-baseos-rpms baseurl=http://server.example.com/rhel8/BaseOS/ [AppStream] name=rhel-8-for-x86_64-appstream-rpms baseurl=http://server.example.com/rhel8/AppStream/ /etc/yum.repos.d/satellite.repo: <<<<<<<<OR capsule [satellite-6.11-for-rhel-8-x86_64-rpms] name=satellite-6.11-for-rhel-8-x86_64-rpms baseurl=http://server.example.com/sat6/Satellite/ [satellite-maintenance-6.11-for-rhel-8-x86_64-rpms] name=satellite-maintenance-6.11-for-rhel-8-x86_64-rpms baseurl=http://server.example.com/sat6/Maintenance/ Let Leapp analyze your system: # leapp preupgrade \ --no-rhsm \ --enablerepo BaseOS \ --enablerepo AppStream \ --enablerepo satellite-6.11-for-rhel-8-x86_64-rpms \ --enablerepo satellite-maintenance-6.11-for-rhel-8-x86_64-rpms The first run is expected to fail but report issues and inhibit the upgrade. Examine the report in the /var/log/leapp/leapp-report.txt file, answer all questions (using leapp answer), and manually resolve the other reported problems. The following commands show the most common steps required: # rmmod pata_acpi # echo PermitRootLogin yes | tee -a /etc/ssh/sshd_config # leapp answer --section remove_pam_pkcs11_module_check.confirm=True If leapp preupgrade inhibits the upgrade with Unsupported network configuration because there are multiple legacy named network interfaces, follow the instructions shown by Leapp to rename the interfaces, followed by an installer run to reconfigure Satellite or Capsule to use the new interface names: # satellite-installer --help |grep 'interface.*eth' --foreman-proxy-dhcp-interface DHCP listen interface (current: "eth0") --foreman-proxy-dns-interface DNS interface (current: "eth0") If eth0 was renamed to em0, call the installer to use the new interface name with: # satellite-installer --foreman-proxy-dhcp-interface=em0 --foreman-proxy-dns-interface=em0 Ensure leapp preupgrade has no issues. Run: # leapp upgrade \ --no-rhsm \ --enablerepo BaseOS \ --enablerepo AppStream \ --enablerepo satellite-6.11-for-rhel-8-x86_64-rpms \ --enablerepo satellite-maintenance-6.11-for-rhel-8-x86_64-rpms > AFTER the leapp upgrade Leapp finishes the upgrade, watch it with: # journalctl -u leapp_resume -f Reindex the databases: # runuser -u postgres -- reindexdb -a Complete these procedures in Upgrading from RHEL 7 to RHEL 8: Verifying the post-upgrade state of the RHEL 8 system Performing post-upgrade tasks For Satellite only and not Capsule, if you require SELinux to be in enforcing mode, run the following command before changing SELinux to enforcing mode: # dnf reinstall foreman-selinux katello-selinux --disableplugin=foreman-protector Complete the steps for changing SELinux to enforcing mode described in Changing SELinux mode to enforcing in the Upgrading from RHEL 7 to RHEL 8 guide.
Hello, Many thanks for the feedback and the suggestion for improvement. The Bz will go though proper team triage and will be picked up based on current capacities. Important updates about the progress o nthe implementation of the fix will be shared here. Thank you!