Red Hat Satellite Minor Version Upgrade Best Practice - Satellites and Capsules
Hi there,
A quick question on the best practice for upgrading Red Hat Satellite and Capsule servers. I know that I need to keep the versions in sync and I know that I need to run "katello-installer --upgrade" or "capsule-installer --upgrade" after the packages are updated.
An example, upgrading from 6.1.6 to 6.1.7 RHSA-2016:0174 can anyone comment whether these steps are appropriate for a Satellite Server and Capsule running on RHEL 7.2?
Synchronize the following repos on the Satellite server if not synchronized recently:
Red Hat Enterprise Linux 7 Server (RPMs)
Red Hat Satellite Capsule 6.1 (for RHEL 7 Server) (RPMs)
On the satellite server:
- katello-service stop (Any need to do this?)
- yum update (If kernel updates are applied should I reboot after this point or do this as a final step?)
- katello-installer --upgrade
- Check whether any tuning parameters need to be reapplied Red Hat Bugzilla 1273168
- katello-service start (Depending on if I stopped earlier)
Once the server is complete, update the capsule:
- katello-service stop (Any need to do this?)
- yum update (If kernel updates are applied should I reboot after this point or do this as a final step?)
- capsule-installer --upgrade
- Check whether any tuning parameters need to be reapplied Red Hat Bugzilla 1273168
- katello-service start (Depending on if I stopped earlier)
I presume it's OK to have the Satellite server on 6.1.7 and the capsule on 6.1.6 for a short period as would be the case in the above procedure? Or should I shutdown the Satellite services on the capsule server before I begin.
Many thanks,
Richard.
Responses
Expert
929 points
In my experience this has worked since 6.1.1. 6.1.0 to 6.1.1 didn't work too well, so I reinstalled at that point. The capsules will have to be out of sync at least temporarily.
The one thing I would add is that any customization to named or dhcpd on your capsules will also get wiped during upgrade and you'll need to replace them
Red Hat
Guru
2300 points
You can preserve your custom configurations by using the following switches.
--capsule-dhcp-managed DHCP is managed by Foreman proxy (default: true)
--capsule-dns-managed DNS is managed by Foreman proxy (default: true)
At installation, you've used the --capsule-dns or --capsule-dhcp switches to enable DNS/DHCP integration. Run katello-installer again with the respective switch(es) set to false to protect your custom configurations.
With respect to the original post, comments (and slight reordering) below.
katello-service stop (Any need to do this?)
Definitely not a need. But if it makes you happy :)
yum update (If kernel updates are applied should I reboot after this point or do this as a final step?)
Wait on the reboot. (Because we do not want the services back online prior to running katello-installer --upgrade)
Check whether any tuning parameters need to be reapplied Red Hat Bugzilla 1273168
you can run the installer in noop mode katello-installer --noop --verbose --upgrade to identify which configurations will be overwritten prior to beginning.
katello-installer --upgrade
Note: katello-installer will 'do the right thing' regardless of the state of the services. Example: if in your first step, you stopped the services and one or more of them need to be online for the upgrade to complete. (such as MongoDB when performing migrations in pulp), they will be started.
katello-service start (Depending on if I stopped earlier)
This step is not needed. the upgrade process does a full start (or restart) of the services.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.