Capsule Upgrade

Katello supports upgrades from version 2.0. For users transitioning from 1.4, please see - Transition Guide.

Step 1 - Operating System

Ensure your operating system is fully up-to-date:

yum -y update

NOTE: If kernel packages are updated here (e.g. upgrading el 6.6 to 6.7), you must reboot and ensure the new kernel and SELinux policy is loaded before upgrading Katello.

Step 2 - Repositories

Update the Foreman and Katello release packages:

• RHEL6 / CentOS 6:

  yum update -y https://fedorapeople.org/groups/katello/releases/yum/2.4/katello/RHEL/6Server/x86_64/katello-repos-latest.rpm
  yum update -y https://yum.theforeman.org/releases/1.1/el6/x86_64/foreman-release.rpm

• RHEL7 / CentOS 7:

  yum update -y https://fedorapeople.org/groups/katello/releases/yum/2.4/katello/RHEL/7Server/x86_64/katello-repos-latest.rpm
  yum update -y https://yum.theforeman.org/releases/1.1/el7/x86_64/foreman-release.rpm

Step 3 - Update Packages

Clean the yum cache

yum clean all

Update packages:

yum update -y

Step 4 - Regenerate Certificates

On the Katello server, regenerate the certificates tarball for your capsule:

capsule-certs-generate --capsule-fqdn "mycapsule.example.com"\
                       --certs-tar    "~/mycapsule.example.com-certs.tar"

And copy them to your capsule:

scp ~/mycapsule.example.com-certs.tar mycapsule.example.com:

Step 5 - Run Installer

The installer with the –upgrade flag will run the right database migrations for all component services, as well as adjusting the configuration to reflect what’s new in Katello 2.4

capsule-installer --upgrade --certs-tar ~/mycapsule.example.com-certs.tar\
                  --certs-update-all --regenerate --deploy

Congratulations! You have now successfully upgraded your Capsule to 2.4 For a rundown of what was added, please see release notes.!

If for any reason, the above steps failed, please review /var/log/capsule-installer/capsule-installer.log – if any of the “Upgrade step” tasks failed, you may try to run them manaully below to aid in troubleshooting.

Manual Steps

Pulp

sudo -u apache pulp-manage-db