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 MongoDB and 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 the satellite-maintain 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-satellite-6.5-rpms

5. Install the satellite-clone package

   # satellite-maintain packages 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, TFTP in the Satellite web UI. For more information, see Configuring DNS, DHCP, and TFTP on Satellite Server in Installing Satellite Server from a Connected Network.

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. 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 hostname to the source server’s hostname. If you want to change the hostname 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.

Upgrade Satellite Server

1. Create a backup.

   • On a virtual machine, take a snapshot.

   • On a physical machine, create a backup.

     For more information about backups, see Backing Up and Restoring Satellite Server and Capsule Server in the Administering Red Hat Satellite 6.5 guide.

2. Back up the DNS and DHCP configuration files /etc/zones.conf and /etc/dhcp/dhcpd.conf as the installer only supports one domain or subnet, and therefore restoring changes from these backups might be required.

3. If you have 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

4. 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.

5. Clean yum cache:

   # yum clean all

6. Ensure that the rubygem-foreman_maintain package that provides satellite-maintain is installed and up to date:

   # yum install rubygem-foreman_maintain

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

   # satellite-maintain upgrade list-versions

8. 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.6

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

9. Because of the lengthy upgrade time, use a utility such as screen to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. For more information about using the screen command, see How do I use the screen command? article in the Red Hat Knowledge Base.

   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.

10. Perform the upgrade:

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

11. Check when the kernel packages were last updated:

    # rpm -qa --last | grep kernel

12. Optional: If a kernel update occurred since the last reboot, stop the satellite-maintain services and reboot the system:

    # satellite-maintain service stop
    # reboot

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

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

14. Check and restore any changes required to the DNS and DHCP configuration files using the backups that you make.

15. If you make changes in the previous step, restart the satellite-maintain services.

    # satellite-maintain service restart

16. 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

Upgrade Disconnected Satellite Server

1. Create a backup.

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

2. 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

   If the upgrade check reports a failure due to running tasks, then it is recommended that you wait for the tasks to complete. It is possible to cancel some tasks, but you should follow the guidance in the Red Hat Knowledgebase solution How to manage paused tasks on Red Hat Satellite 6 to understand which tasks are safe to cancel and which are not safe to cancel.

3. Back up the DNS and DHCP configuration files /etc/zones.conf and /etc/dhcp/dhcpd.conf as the installer only supports one domain or subnet, and therefore restoring changes from these backups might be required.

4. If you have made manual edits to DNS or DHCP configuration files and do not want to overwrite the changes, run the installer script as follows:

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

5. 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.
6. Make sure all external Capsule Servers are assigned to an organization, otherwise they might get unregistered due to host-unification changes.

7. Remove old repositories:

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

8. Stop the satellite-maintain services.

   # satellite-maintain service stop

9. Obtain the latest ISO files by following the Downloading the Binary DVD Images procedure in the Installing Satellite Server from a Disconnected Network guide.
10. Create directories to serve as a mount point, mount the ISO images, and configure the rhel7-server repository by following the Configuring the Base System with Offline Repositories procedure in the Installing Satellite Server from a Disconnected Network guide. Do not install or update any packages at this stage.

11. Configure the Satellite 6.6 repository from the ISO file.

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

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

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

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

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

          [Satellite-6.6]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/

12. 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/

13. 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/sat-maintenance/media.repo /etc/yum.repos.d/sat-maintenance.repo

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

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

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

          [Satellite-Maintenance]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/sat-maintenance/

14. 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 and rh-mongodb34-mongod database services.

       # systemctl start postgresql
       # systemctl start rh-mongodb34-mongod

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

       # satellite-installer --scenario satellite --upgrade --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 the satellite-maintain services:

       # satellite-maintain service stop

15. Because of the lengthy upgrade time, use a utility such as screen to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. For more information about using the screen command, see How do I use the screen command? article in the Red Hat Knowledge Base.

    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.

16. Clean yum cache:

    # yum clean all

17. Ensure that the rubygem-foreman_maintain package that provides satellite-maintain is installed and up to date:

    # yum install rubygem-foreman_maintain

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

    # satellite-maintain upgrade list-versions

19. 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.6 \
    --whitelist="repositories-validate,repositories-setup"

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

20. Perform the upgrade:

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

    Warning

    If you run the command from a directory containing a config subdirectory, you will encounter the following error:

    ERROR: Scenario (config/satellite.yaml) was not found, can not continue.

    In such a case, change directory, for example to the root user’s home directory, and run the command again.

    If the script fails due to missing or outdated packages, you must download and install these separately. For more information, see the Downloading Packages Manually section in the Installing Satellite Server from a Disconnected Network guide.

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

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

22. Check when the kernel packages were last updated:

    # rpm -qa --last | grep kernel

23. Optional: If a kernel update occurred since the last reboot, stop the satellite-maintain services and reboot the system:

    # satellite-maintain service stop
    # reboot

24. Check and restore any changes required to the DNS and DHCP configuration files using the backups that you make.

25. If you make changes in the previous step, restart the satellite-maintain services.

    # satellite-maintain service restart

26. 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

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

1. Update the Discovery template in the Satellite web UI:

   1. Navigate to Hosts > Provisioning templates.
   2. On the PXELinux global default line, click Clone.
   3. Enter a new name for the template in the Name field, for example ACME PXE global default.
   4. In the template editor field, change the line ONTIMEOUT local to ONTIMEOUT discovery and click Submit.
   5. Navigate to Administer > Settings.
   6. Locate Global default PXELinux template and click on its Value.
   7. Select the name of the newly created template from the menu and click the tick button.
   8. Navigate to Hosts > Provisioning templates.
   9. Click Build PXE Default, then click OK.
2. 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.

   # yum upgrade 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.

   # yum upgrade foreman-discovery-image

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

   # yum install 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.

Ensure all subnets with discovered hosts have a template Capsule:

1. In the Satellite web UI, navigate to Infrastructure > Subnets.
2. Select the subnet you want to check.
3. On the Capsules tab, ensure a Template Capsule has been set for this subnet.