8.2. Upgrading Red Hat Satellite Capsule

Procedure 8.5. To Upgrade Red Hat Satellite Capsule:

  1. Update the operating system:
    # yum update
    
  2. Disable the repositories for the previous version of Satellite.
    • If upgrading from Satellite 6.0 on Red Hat Enterprise Linux 7:
      # subscription-manager repos --disable rhel-7-server-satellite-capsule-6.0-rpms
    • If upgrading from Satellite 6.1 Beta on Red Hat Enterprise Linux 7:
      # subscription-manager repos --disable rhel-server-7-satellite-capsule-6-beta-rpms
    • If upgrading from Satellite 6.0 on Red Hat Enterprise Linux 6:
      # subscription-manager repos --disable rhel-6-server-satellite-capsule-6.0-rpms
    • If upgrading from Satellite 6.1 Beta on Red Hat Enterprise Linux 6:
      # subscription-manager repos --disable rhel-server-6-satellite-capsule-6-beta-rpms
  3. Enable the new repositories.
    • On Red Hat Enterprise Linux 7:
      # subscription-manager repos --enable rhel-7-server-satellite-capsule-6.1-rpms
    • On Red Hat Enterprise Linux 6:
      # subscription-manager repos --enable rhel-6-server-satellite-capsule-6.1-rpms
  4. If there are discovered hosts available, turn them off and delete all entries under the Discovered hosts page.
  5. Stop the following services to prevent dependency errors during the database migration:
    # for i in qpidd pulp_workers pulp_celerybeat pulp_resource_manager httpd; do service $i stop; done
    
  6. Clear the repository cache and update all packages:
    # yum clean all
    # yum update
    
  7. The following steps are required only if you upgrade from Satellite 6.0:
    1. Install the capsule-installer package:
      # yum install capsule-installer

      Note

      In Red Hat Satellite 6.0, the katello-installer script provided the Satellite Capsule Server installer. In Satellite 6.1, the capsule-installer script has its own package.
      Installing capsule-installer automatically removes the katello-installer package and saves the previous Capsule configuration and answer files.
    2. Copy the previous answer file to the new capsule-installer directory:
      # cp /etc/katello-installer/answers.capsule-installer.yaml.rpmsave /etc/capsule-installer/answers.capsule-installer.yaml
  8. On the Satellite Server, generate an archive with new certificates:
    # capsule-certs-generate --capsule-fqdn "capsule.example.com" --certs-tar "capsule.example.com-certs.tar"
    Replace capsule.example.com with the fully qualified domain name of the Capsule. Copy the archive file to the Capsule.
  9. Install the Discovery plug-in if you plan to use the Capsule as a proxy for discovered hosts:
    # yum install rubygem-smart_proxy_discovery.noarch
  10. Verify if the foreman_url setting refers to the Satellite Server correctly. On the Capsule execute:
    # grep foreman_url /etc/foreman-proxy/settings.yml
    The above command should return the fully qualified domain name (FQDN) of the Satellite server, for example:
    :foreman_url: https://satellite.example.com
  11. Restart the foreman-proxy component on the Satellite Capsule server:
    # service foreman-proxy restart
  12. Run the installer with the --upgrade option:
    # capsule-installer --upgrade --certs-tar capsule.example.com-certs.tar
    Replace capsule.example.com-certs.tar with the path to the certificate archive on the Capsule.

    Important

    If you have made manual edits to DNS and DHCP configuration files, they will be overwritten during the upgrade process. To avoid this, append the --dns-managed=false and --dhcp-managed=false options to the --upgrade installer command.
  13. Upgrade the foreman-discovery-image package on the Satellite server and turn on the hosts that were shut down prior the upgrade.