I am postive that these steps would no longer be required in Satellite 6.12 and 6.13 ( and even for 6.11 running on RHEL 8 ) Reported by: rhn-support-saydas https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/upgrading_and_updating_red_hat_satellite/upgrading_satellite#annotations:240661e9-1988-4ad0-b33d-8f9c73a6da9f
Doc links: Sat 6.12 https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/upgrading_and_updating_red_hat_satellite/upgrading_satellite#upgrading_a_disconnected_satellite "3.1.2. Upgrading a Disconnected Satellite Server" Sat 6.13 https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/upgrading_and_updating_red_hat_satellite/index?lb_target=preview 2.1.2. Upgrading a Disconnected Satellite Server Satellite 6.12 and Satellite 6.13 runs on RHEL 8 and should not require the creation of /etc/yum.repos.d/ansible.repo or /etc/yum.repos.d/RHSCL.repo files for upgrade. To support my statement: The ISO of 6.12.1 contains the following and The 6.13 ISO ( when released ) is expected to contain a similar directory structure: $ sudo mount -o loop Downloads/Satellite-6.12.1-rhel-8-x86_64.dvd.iso /mnt mount: /mnt: WARNING: device write-protected, mounted read-only. $ ll /mnt total 10 -r-xr-xr-x. 1 root root 4506 Jan 17 19:48 install_packages dr-xr-xr-x. 4 root root 2048 Jan 17 19:52 Maintenance -r--r--r--. 1 root root 893 Jan 17 19:52 TRANS.TBL dr-xr-xr-x. 4 root root 2048 Jan 17 19:52 Satellite $ ll /mnt/Satellite/ total 100 -r--r--r--. 2 root root 141 Jan 17 19:52 media.repo dr-xr-xr-x. 2 root root 4096 Jan 17 19:52 repodata dr-xr-xr-x. 2 root root 96256 Jan 17 19:52 Packages -r--r--r--. 1 root root 1104 Jan 17 19:52 TRANS.TBL $ ll /mnt/Maintenance/ total 8 -r--r--r--. 2 root root 141 Jan 17 19:52 media.repo dr-xr-xr-x. 2 root root 4096 Jan 17 19:52 repodata dr-xr-xr-x. 2 root root 2048 Jan 17 19:52 Packages -r--r--r--. 1 root root 1104 Jan 17 19:52 TRANS.TBL So we should fix\remove the unnecessary steps from the Disconnected upgrade guide or Satellite 6.13 and 6.12
*** Bug 2169497 has been marked as a duplicate of this bug. ***