Upgrading and Updating Red Hat Satellite

1. Verify the Pool ID of your Satellite subscription:

   # subscription-manager list --consumed \
   --matches 'Red Hat Satellite'|grep "Pool ID:"|awk '{print $3}'

   Note the Pool ID for later use.

2. Remove the Red Hat Satellite subscription:

   # subscription-manager remove --serial=$(subscription-manager list \
   --consumed \
   --matches 'Red Hat Satellite'|grep "Serial:"|awk '{print $2}')

3. Determine the size of the Pulp data:

   # du -sh /var/lib/pulp/

4. If you have less than 500 GB of Pulp data, perform a backup with PostgreSQL databases active including the Pulp data. If you have more than 500 GB of Pulp data, skip the following steps and complete the steps in Section 2.3, “Pulp Data Considerations” before you continue.

   # satellite-maintain backup offline --assumeyes /var/backup

5. Stop and disable Satellite services:

   # satellite-maintain service stop
   # satellite-maintain service disable

1. The satellite-clone tool defaults to using /backup/ as the backup folder. If you copy to a different folder, update the backup_dir variable in the /etc/satellite-clone/satellite-clone-vars.yml file.
2. Place the backup files from the source Satellite in the /backup/ folder on the target server. You can either mount the shared storage or copy the backup files to the /backup/ folder on the target server.
3. Power off the source server.

4. Enter the following commands to register to the Customer Portal, attach subscriptions, and enable only the required subscriptions:

   # subscription-manager register your_customer_portal_credentials
   # subscription-manager attach --pool=pool_ID
   # subscription-manager repos --disable=*
   # subscription-manager repos \
   --enable=rhel-7-server-rpms \
   --enable=rhel-server-rhscl-7-rpms \
   --enable=rhel-7-server-satellite-maintenance-6-rpms \
   --enable=rhel-7-server-ansible-2.9-rpms \
   --enable=rhel-7-server-satellite-6.10-rpms

5. Install the satellite-clone package:

   # yum install satellite-clone

   After you install the satellite-clone tool, you can adjust any configuration to suit your own deployment in the /etc/satellite-clone/satellite-clone-vars.yml file.

6. Run the satellite-clone tool:

   # satellite-clone

7. Reconfigure DHCP, DNS, TFTP, and remote execution services. The cloning process disables these services on the target Satellite Server to avoid conflict with the source Satellite Server.
8. Reconfigure and enable DHCP, DNS, and TFTP in the Satellite web UI. For more information, see Configuring External Services on Satellite Server in Installing Satellite Server.

9. Enable remote execution:

   # satellite-installer --scenario satellite \
   --enable-foreman-plugin-remote-execution \
   --enable-foreman-proxy-plugin-remote-execution-ssh

10. Log on to the Satellite web UI, with the username admin and the password changeme. Immediately update the admin password to secure credentials.
11. Ensure that the correct organization is selected.
12. In the Satellite web UI, navigate to Content > Subscriptions, then click Manage Manifest.
13. Click the Refresh button, then click Close to return to the list of subscriptions.
14. Verify that the available subscriptions are correct.
15. Follow the instructions in the /usr/share/satellite-clone/logs/reassociate_capsules.txt file to restore the associations between Capsules and their lifecycle environments.
16. Update your network configuration, for example, DNS, to match the target server’s IP address with its new host name. The satellite-clone tool changes the host name to the source server’s host name. If you want to change the host name to something different, you can use the satellite-change-hostname tool. For more information, see Renaming a Satellite or Capsule Server in Administrating Red Hat Satellite.
17. If the source server uses the virt-who daemon, install and configure it on the target server. Copy all the virt-who configuration files in the /etc/virt-who.d/ directory from the source server to the same directory on the target server. For more information, see Configuring Virtual Machine Subscriptions in Red Hat Satellite. After you perform an upgrade using the following chapters, you can safely decommission the source server.

Upgrade Satellite Server

1. Stop all Satellite services:

   # satellite-maintain service stop

2. Take a snapshot or create a backup:

   • On a virtual machine, take a snapshot.
   • On a physical machine, create a backup.

3. Start all Satellite services:

   # satellite-maintain service start

4. Optional: If you made manual edits to DNS or DHCP configuration in the /etc/zones.conf or /etc/dhcp/dhcpd.conf files, back up the configuration files because the installer only supports one domain or subnet, and therefore restoring changes from these backups might be required.

5. Optional: If you made manual edits to DNS or DHCP configuration files and do not want to overwrite the changes, enter the following command:

   # satellite-installer --foreman-proxy-dns-managed=false \
   --foreman-proxy-dhcp-managed=false

6. In the Satellite web UI, navigate to Hosts > Discovered hosts. On the Discovered Hosts page, power off and then delete the discovered hosts. From the Select an Organization menu, select each organization in turn and repeat the process to power off and delete the discovered hosts. Make a note to reboot these hosts when the upgrade is complete.

7. Ensure that the Satellite Maintenance repository is enabled:

   # subscription-manager repos --enable \
   rhel-7-server-satellite-maintenance-6.11-rpms

8. Check the available versions to confirm the version you want is listed:

   # satellite-maintain upgrade list-versions

9. Use the health check option to determine if the system is ready for upgrade. When prompted, enter the hammer admin user credentials to configure satellite-maintain with hammer credentials. These changes are applied to the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

   # satellite-maintain upgrade check --target-version 6.11

   Review the results and address any highlighted error conditions before performing the upgrade.

10. Because of the lengthy upgrade time, use a utility such as tmux to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously.

    If you lose connection to the command shell where the upgrade command is running you can see the logged messages in the /var/log/foreman-installer/satellite.log file to check if the process completed successfully.

11. Perform the upgrade:

    # satellite-maintain upgrade run --target-version 6.11

12. Determine if the system needs a reboot:

    1. Check the version of newest installed kernel:

       # rpm --query --last kernel | head -n 1

    2. Compare this to the version of currently running kernel:

       # uname --kernel-release

13. Optional: If the newest kernel differs from the currently running kernel, reboot the system:

    # reboot

14. If using a BASH shell, after a successful or failed upgrade, enter:

    # hash -d satellite-maintain service 2> /dev/null

Upgrade Disconnected Satellite Server

1. Stop all Satellite services:

   # satellite-maintain service stop

2. Take a snapshot or create a backup:

   • On a virtual machine, take a snapshot.
   • On a physical machine, create a backup.

3. Start all Satellite services:

   # satellite-maintain service start

4. A pre-upgrade script is available to detect conflicts and list hosts which have duplicate entries in Satellite Server that can be unregistered and deleted after upgrade. In addition, it will detect hosts which are not assigned to an organization. If a host is listed under Hosts > All hosts without an organization association and if a content host with same name has an organization already associated with it then the content host will automatically be unregistered. This can be avoided by associating such hosts to an organization before upgrading.

   Run the pre-upgrade check script to get a list of hosts that can be deleted after upgrading. If any unassociated hosts are found, associating them to an organization before upgrading is recommended.

   # foreman-rake katello:upgrade_check

5. Optional: If you made manual edits to DNS or DHCP configuration in the /etc/zones.conf or /etc/dhcp/dhcpd.conf files, back up the configuration files because the installer only supports one domain or subnet, and therefore restoring changes from these backups might be required.

6. Optional: If you made manual edits to DNS or DHCP configuration files and do not want to overwrite the changes, enter the following command:

   # satellite-installer --foreman-proxy-dns-managed=false \
   --foreman-proxy-dhcp-managed=false

7. In the Satellite web UI, navigate to Hosts > Discovered hosts. If there are discovered hosts available, turn them off and then delete all entries under the Discovered hosts page. Select all other organizations in turn using the organization setting menu and repeat this action as required. Reboot these hosts after the upgrade has completed.
8. Make sure all external Capsule Servers are assigned to an organization, otherwise they might get unregistered due to host-unification changes.

9. Remove old repositories:

   # rm /etc/yum.repos.d/*

10. Stop Satellite services:

    # satellite-maintain service stop

11. Obtain the latest ISO files by following the Downloading the Binary DVD Images procedure in Installing Satellite Server in a Disconnected Network Environment.

12. Create directories to serve as a mount point, mount the ISO images, and configure the rhel7-server or the rhel8 repository:

    For Red Hat Enterprise Linux 8

    Follow the Configuring the Base Operating System with Offline Repositories in RHEL 8 procedure in Installing Satellite Server in a Disconnected Network Environment.

    For Red Hat Enterprise Linux 7

    Follow the Configuring the Base Operating System with Offline Repositories in RHEL 7 procedure in Installing Satellite Server in a Disconnected Network Environment.

    Do not install or update any packages at this stage.

13. Configure the Satellite 6.11 repository from the ISO file.

    1. Copy the ISO file’s repository data file for the Red Hat Satellite packages:

       # cp /media/sat6/Satellite/media.repo /etc/yum.repos.d/satellite.repo

    2. Edit the /etc/yum.repos.d/satellite.repo file:

       # vi /etc/yum.repos.d/satellite.repo

       1. Change the default InstallMedia repository name to Satellite-6.11:

          [Satellite-6.11]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/Satellite

14. Configure the Red Hat Satellite Maintenance repository from the ISO file.

    1. Copy the ISO file’s repository data file for Red Hat Satellite Maintenance packages:

       # cp /media/sat6/Maintenance/media.repo /etc/yum.repos.d/satellite-maintenance.repo

    2. Edit the /etc/yum.repos.d/satellite-maintenance.repo file:

       # vi /etc/yum.repos.d/satellite-maintenance.repo

       1. Change the default InstallMedia repository name to Satellite-Maintenance:

          [Satellite-Maintenance]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/Maintenance/

15. If your Satellite runs on Red Hat Enterprise Linux 7, configure the Ansible repository from the ISO file.

    1. Copy the ISO file’s repository data file for Ansible packages:

       # cp /media/sat6/ansible/media.repo /etc/yum.repos.d/ansible.repo

    2. Edit the /etc/yum.repos.d/ansible.repo file:

       # vi /etc/yum.repos.d/ansible.repo

       1. Change the default InstallMedia repository name to Ansible:

          [Ansible]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/ansible/

16. If your Satellite runs on Red Hat Enterprise Linux 7, configure the Red Hat Software Collections repository from the ISO file.

    1. Copy the ISO file’s repository data file for Red Hat Software Collections packages:

       # cp /media/sat6/RHSCL/media.repo /etc/yum.repos.d/RHSCL.repo

    2. Edit the /etc/yum.repos.d/RHSCL.repo file:

       # vi /etc/yum.repos.d/RHSCL.repo

       1. Change the default InstallMedia repository name to RHSCL:

          [RHSCL]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/RHSCL/

17. Optional: If you have applied custom Apache server configurations, note that the custom configurations are reverted to the installation defaults when you perform the upgrade.

    To preview the changes that are applied during the upgrade, enter the satellite-installer command with the --noop (no operation) option. These changes are applied when you enter the satellite-maintain upgrade command in a following step.

    1. Add the following line to the /etc/httpd/conf/httpd.conf configuration file.

       Include /etc/httpd/conf.modules.d/*.conf

    2. Restart the httpd service.

       # systemctl restart httpd

    3. Start the postgresql database services.

       # systemctl start postgresql

    4. Enter the satellite-installer command with the --noop option:

       # satellite-installer --scenario satellite --verbose --noop

       Review the /var/log/foreman-installer/satellite.log to preview the changes that are applied during the upgrade. Locate the +++ and --- symbols that indicate the changes to the configurations files. Although entering the satellite-installer command with the --noop option does not apply any changes to your Satellite, some Puppet resources in the module expect changes to be applied and might display failure messages.

    5. Stop Satellite services:

       # satellite-maintain service stop

18. Because of the lengthy upgrade time, use a utility such as tmux to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously.

    If you lose connection to the command shell where the upgrade command is running you can see the logs in /var/log/foreman-installer/satellite.log to check if the process completed successfully.

19. Check the available versions to confirm the version you want is listed:

    # satellite-maintain upgrade list-versions

20. Use the health check option to determine if the system is ready for upgrade. When prompted, enter the hammer admin user credentials to configure satellite-maintain with hammer credentials. These changes are applied to the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

    # satellite-maintain upgrade check --target-version 6.11 \
    --whitelist="repositories-validate,repositories-setup"

    Review the results and address any highlighted error conditions before performing the upgrade.

21. Perform the upgrade:

    # satellite-maintain upgrade run --target-version 6.11 \
    --whitelist="repositories-validate,repositories-setup"

    If the script fails due to missing or outdated packages, you must download and install these separately. For more information, see Resolving Package Dependency Errors in Installing Satellite Server in a Disconnected Network Environment.

22. If using a BASH shell, after a successful or failed upgrade, enter:

    # hash -d satellite-maintain service 2> /dev/null

23. Check when the kernel packages were last updated:

    # rpm -qa --last | grep kernel

24. Optional: If a kernel update occurred since the last reboot, stop Satellite services and reboot the system:

    # satellite-maintain service stop
    # reboot

25. Optional: If you made manual edits to DNS or DHCP configuration files, check and restore any changes required to the DNS and DHCP configuration files using the backups that you made.

26. If you make changes in the previous step, restart Satellite services:

    # satellite-maintain service restart

27. If you have the OpenSCAP plug-in installed, but do not have the default OpenSCAP content available, enter the following command.

    # foreman-rake foreman_openscap:bulk_upload:default

28. In the Satellite web UI, go to Configure > Discovery Rules and associate selected organizations and locations with discovery rules.

1. Verify that the Foreman Discovery package is current on Satellite Server.

   # satellite-maintain packages install tfm-rubygem-foreman_discovery

2. If an update occurred in the previous step, restart the satellite-maintain services.

   # satellite-maintain service restart

3. Upgrade the Discovery image on the Satellite Capsule that is either connected to the provisioning network with discovered hosts or provides TFTP services for discovered hosts.

   # satellite-maintain packages install foreman-discovery-image

4. On the same instance, install the package which provides the Proxy service, and then restart foreman-proxy service.

   # satellite-maintain packages install tfm-rubygem-smart_proxy_discovery
   # service foreman-proxy restart

5. In the Satellite web UI, go to Infrastructure > Capsules and verify that the relevant Capsule lists Discovery in the features column. Select Refresh from the Actions drop-down menu if necessary.

6. Go to Infrastructure > Subnets and for each subnet on which you want to use discovery:

   1. Click the subnet name.
   2. On the Capsules tab, ensure the Discovery Capsule is set to a Capsule you configured above.

Upgrade virt-who Manually

1. Upgrade virt-who.

   # yum upgrade virt-who

2. Restart the virt-who service so the new version is activated.

   # systemctl restart virt-who.service

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. In the Enabled Repositories area, locate Red Hat Satellite Tools 6.10 for RHEL 7 Server RPMs x86_64.
3. Click the Disable icon to the right.

Procedure

1. Stop all services, except for the postgresql service:

   # satellite-maintain service stop --exclude postgresql

2. Switch to the postgres user and reclaim space on the database:

   # su - postgres -c 'vacuumdb --full --all'

3. Start the other services when the vacuum completes:

   # satellite-maintain service start

1. The default tuning profile defined in the /usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml file
2. The tuning profile that you want to apply to your deployment and is defined in the /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/ directory
3. Optional: If you have configured a /etc/foreman-installer/custom-hiera.yaml file, Satellite applies these configuration settings.

Procedure

1. Optional: If you have configured the custom-hiera.yaml file on Satellite Server, back up the /etc/foreman-installer/custom-hiera.yaml file to custom-hiera.original. You can use the backup file to restore the /etc/foreman-installer/custom-hiera.yaml file to its original state if it becomes corrupted:

   # cp /etc/foreman-installer/custom-hiera.yaml \
   /etc/foreman-installer/custom-hiera.original

2. Optional: If you have configured the custom-hiera.yaml file on Satellite Server, review the definitions of the default tuning profile in /usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml and the tuning profile that you want to apply in /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/. Compare the configuration entries against the entries in your /etc/foreman-installer/custom-hiera.yaml file and remove any duplicated configuration settings in your /etc/foreman-installer/custom-hiera.yaml file.

3. Enter the satellite-installer command with the --tuning option for the profile that you want to apply. For example, to apply the medium tuning profile settings, enter the following command:

   # satellite-installer --tuning medium

1. Ensure that you have synchronized the following repositories in your connected Satellite Server.

   rhel-8-for-x86_64-baseos-rpms
   rhel-8-for-x86_64-appstream-rpms
   satellite-6.11-for-rhel-8-x86_64-rpms
   satellite-maintenance-6.11-for-rhel-8-x86_64-rpms

2. Download the debug certificate of the organization and store it locally at, for example, /etc/pki/katello/certs/org-debug-cert.pem or a location of your choosing. For more information, see Creating an Organization Debug Certificate in Managing Content.

3. Create a Yum configuration file under /etc/yum.repos.d, such as satellite-disconnected.repo, with the following contents:

   [rhel-8-for-x86_64-baseos-rpms]
   name=Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs)
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel8/8/x86_64/baseos/os
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1
   
   [rhel-8-for-x86_64-appstream-rpms]
   name=Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs)
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel8/8/x86_64/appstream/os
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1
   
   [satellite-6.11-for-rhel-8-x86_64-rpms]
   name=Red Hat Satellite 6.11 for RHEL 8 RPMs x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/layered/rhel8/x86_64/satellite/6.11/os
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   
   [satellite-maintenance-6.11-for-rhel-8-x86_64-rpms]
   name=Red Hat Satellite Maintenance 6.11 for RHEL 8 RPMs x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/layered/rhel8/x86_64/sat-maintenance/6.11/os
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1

4. In the configuration file, replace /etc/pki/katello/certs/org-debug-cert.pem in sslclientcert and sslclientkey with the location of the downloaded organization debug certificate.
5. Update satellite.example.com with the correct FQDN for your deployment.

6. Replace My_Organization with the correct organization label in the baseurl. To obtain the organization label, enter the command:

   # hammer organization list

7. Enter the reposync command:

   • On Satellite Server running Red Hat Enterprise Linux 7:

     # reposync --delete --download-metadata -p ~/Satellite-repos -n \
      -r rhel-8-for-x86_64-baseos-rpms \
      -r rhel-8-for-x86_64-appstream-rpms \
      -r satellite-6.11-for-rhel-8-x86_64-rpms \
      -r satellite-maintenance-6.11-for-rhel-8-x86_64-rpms

   • On Satellite Server running Red Hat Enterprise Linux 8:

     # reposync --delete --download-metadata -p ~/Satellite-repos -n \
      --repoid rhel-8-for-x86_64-baseos-rpms \
      --repoid rhel-8-for-x86_64-appstream-rpms \
      --repoid satellite-6.11-for-rhel-8-x86_64-rpms \
      --repoid {RepoRHEL8ServerSatelliteMaintenanceProductVersion

   This downloads the contents of the repositories from the connected Satellite Server and stores them in the ~/Satellite-repos directory.

8. Verify that the RPMs have been downloaded and the repository data directory is generated in each of the sub-directories of ~/Satellite-repos.

9. Archive the contents of the directory

   # cd ~
   # tar czf Satellite-repos.tgz Satellite-repos

10. Use the generated Satellite-repos.tgz file to upgrade in the disconnected Satellite Server.

1. Copy the generated Satellite-repos.tgz file to your disconnected Satellite Server

2. Extract the archive to anywhere accessible by the root user. In the following example /root is the extraction location.

   # cd /root
   # tar zxf Satellite-repos.tgz

3. Create a Yum configuration file under /etc/yum.repos.d, such as satellite-disconnected.repo, with the following contents:

   [rhel-8-for-x86_64-baseos-rpms]
   name=Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs)
   baseurl=file:///root/Satellite-repos/rhel-8-for-x86_64-baseos-rpms
   enabled=1
   
   [rhel-8-for-x86_64-appstream-rpms]
   name=Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs)
   baseurl=file:///root/Satellite-repos/rhel-8-for-x86_64-appstream-rpms
   enabled=1
   
   [satellite-6.11-for-rhel-8-x86_64-rpms]
   name=Red Hat Satellite 6 for RHEL 8 Server RPMs x86_64
   baseurl=file:///root/Satellite-repos/satellite-6.11-for-rhel-8-x86_64-rpms
   enabled=1
   
   [satellite-maintenance-6.11-for-rhel-8-x86_64-rpms]
   name=Red Hat Satellite Maintenance 6 for RHEL 8 Server RPMs x86_64
   baseurl=file:///root/Satellite-repos/satellite-maintenance-6.11-for-rhel-8-x86_64-rpms
   enabled=1

4. In the configuration file, replace the /root/Satellite-repos with the extracted location.

5. Check the available versions to confirm the next minor version is listed:

   # satellite-maintain upgrade list-versions

6. Use the health check option to determine if the system is ready to upgrade. On first use of this command, satellite-maintain prompts you to enter the hammer admin user credentials and saves them in the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

   # satellite-maintain upgrade check --whitelist="check-upstream-repository,repositories-validate" --target-version 6.11.z

7. Review the results and address any highlighted error conditions before performing the upgrade.

8. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously.

   If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the /var/log/foreman-installer/satellite.log file to check if the process was completed successfully.

9. Perform the upgrade:

   # satellite-maintain upgrade run --whitelist="check-upstream-repository,repositories-validate" --target-version 6.11.z

10. Check when the kernel packages were last updated:

    # rpm -qa --last | grep kernel

11. Optional: If a kernel update occurred since the last reboot, stop Satellite services and reboot the system:

    # satellite-maintain service stop
    # reboot

1. Ensure that you have synchronized the following repositories in your connected Satellite Server.

   rhel-7-server-ansible-2.9-rpms
   rhel-7-server-rpms
   rhel-7-server-satellite-6.11-rpms
   rhel-7-server-satellite-maintenance-6.11-rpms
   rhel-server-rhscl-7-rpms

2. Download the debug certificate of the organization and store it locally at, for example, /etc/pki/katello/certs/org-debug-cert.pem or a location of your choosing.

3. Create a Yum configuration file under /etc/yum.repos.d with the following repository information:

   [rhel-7-server-ansible-2.9-rpms]
   name=Ansible 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel/server/7/$releasever/$basearch/ansible/2.9/os/
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1
   
   [rhel-7-server-rpms]
   name=Red Hat Enterprise Linux 7 Server RPMs x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/os/
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1
   
   [rhel-7-server-satellite-6.11-rpms]
   name=Red Hat Satellite 6 for RHEL 7 Server RPMs x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/satellite/6.11/os/
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   
   [rhel-7-server-satellite-maintenance-6.11-rpms]
   name=Red Hat Satellite Maintenance 6 for RHEL 7 Server RPMs x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/sat-maintenance/6/os/
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1
   
   [rhel-server-rhscl-7-rpms]
   name=Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64
   baseurl=https://satellite.example.com/pulp/content/My_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/
   enabled=1
   sslclientcert = /etc/pki/katello/certs/org-debug-cert.pem
   sslclientkey = /etc/pki/katello/certs/org-debug-cert.pem
   sslcacert = /etc/pki/katello/certs/katello-server-ca.crt
   sslverify = 1

4. In the configuration file, replace /etc/pki/katello/certs/org-debug-cert.pem in sslclientcert and sslclientkey with the location of the downloaded organization debug certificate.
5. Update satellite.example.com with correct FQDN for your deployment.

6. Replace My_Organization with the correct organization label in the baseurl. To obtain the organization label, enter the command:

   # hammer organization list

7. Enter the reposync command:

   # reposync --delete --download-metadata -p ~/Satellite-repos -n \
    -r rhel-7-server-ansible-2.9-rpms \
    -r rhel-7-server-rpms \
    -r rhel-7-server-satellite-6.11-rpms \
    -r rhel-7-server-satellite-maintenance-6.11-rpms \
    -r rhel-server-rhscl-7-rpms

   This downloads the contents of the repositories from the connected Satellite Server and stores them in the directory ~/Satellite-repos. The reposync command in Red Hat Enterprise Linux 7 downloads the RPMs but not the Yum metadata.

   Because of this, you must manually run createrepo in each sub-directory of Satellite-repos. Make sure you have the createrepo rpm installed. If not use the following command to install it.

   # satellite-maintain packages install createrepo

   Run the following command to create repodata in each sub-directory of ~/Satellite-repos. :

   # cd ~/Satellite-repos
   # for directory in */
   do
     echo "Processing $directory"
     cd $directory
     createrepo .
     cd ..
   done

8. Verify that the RPMs have been downloaded and the repository data directory is generated in each of the sub-directories of ~/Satellite-repos.

9. Archive the contents of the directory

   # cd ~
   # tar czf Satellite-repos.tgz Satellite-repos

10. Use the generated Satellite-repos.tgz file to upgrade in the disconnected Satellite Server.

1. Copy the generated Satellite-repos.tgz file to your disconnected Satellite Server

2. Extract the archive to anywhere accessible by the root user. In the following example /root is the extraction location.

   # cd /root
   # tar zxf Satellite-repos.tgz

3. Create a Yum configuration file under /etc/yum.repos.d with the following repository information:

   [rhel-7-server-ansible-2.9-rpms]
   name=Ansible 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64
   baseurl=file:///root/Satellite-repos/rhel-7-server-ansible-2.9-rpms
   enabled=1
   
   [rhel-7-server-rpms]
   name=Red Hat Enterprise Linux 7 Server RPMs x86_64
   baseurl=file:///root/Satellite-repos/rhel-7-server-rpms
   enabled=1
   
   [rhel-7-server-satellite-6.11-rpms]
   name=Red Hat Satellite 6 for RHEL 7 Server RPMs x86_64
   baseurl=file:///root/Satellite-repos/rhel-7-server-satellite-6.11-rpms
   enabled=1
   
   [rhel-7-server-satellite-maintenance-6.11-rpms]
   name=Red Hat Satellite Maintenance 6 for RHEL 7 Server RPMs x86_64
   baseurl=file:///root/Satellite-repos/rhel-7-server-satellite-maintenance-6.11-rpms
   enabled=1
   
   [rhel-server-rhscl-7-rpms]
   name=Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64
   baseurl=file:///root/Satellite-repos/rhel-server-rhscl-7-rpms
   enabled=1

4. In the configuration file, replace the /root/Satellite-repos with the extracted location.

5. Check the available versions to confirm the next minor version is listed:

   # satellite-maintain upgrade list-versions

6. Use the health check option to determine if the system is ready for upgrade. On first use of this command, satellite-maintain prompts you to enter the hammer admin user credentials and saves them in the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

   # satellite-maintain upgrade check --whitelist="check-upstream-repository,repositories-validate" --target-version 6.11.z

7. Review the results and address any highlighted error conditions before performing the upgrade.

8. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously.

   If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the /var/log/foreman-installer/satellite.log file to check if the process completed successfully.

9. Perform the upgrade:

   # satellite-maintain upgrade run --whitelist="check-upstream-repository,repositories-setup,repositories-validate" --target-version 6.11.z

10. Check when the kernel packages were last updated:

    # rpm -qa --last | grep kernel

11. Optional: If a kernel update occurred since the last reboot, stop Satellite services and reboot the system:

    # satellite-maintain service stop
    # reboot