Satellite 6.2.15 is now available
Red Hat Satellite 6.2.15 includes bug fixes for improving the performance of Satellite 6.2.x.
There is one erratum for the server  and one for the hosts .
ISOs should be published next week.
Customers who have already upgraded to 6.2 should follow the instructions in the errata. Customers who are on 6.1.x should follow the upgrade instructions in the Satellite 6.2 Installation Guide. Customers who have received hotfixes should verify the list below to ensure their hotfix is contained in the release before upgrading. Please reach out to Red Hat Support in these cases.
Fixes included in 6.2.15
This update fixes the following bugs:
- TLS 1.2 is now enabled by default on Satellite 6.2. (BZ#1331041, BZ#1548093)
- Performance problems with registration, such as concurrent registrations and task blocking have been improved based on work with larger customers. (BZ#1490019, BZ#1514508, BZ#1553845)
- A new dispatch router has been released to fix a segmentation fault caused by long running use. (BZ#1535891)
- Performance problems with the katello-errata query have been improved and backported to Satellite 6.2. (BZ#1518804)
- Performance problems with memory consumption when searching for an unqualified hostgroup have been improved and backported to Satellite 6.2. (BZ#1547986)
- Performance problems with the subscription page when the user has a large volume of hosts have been improved and backported to Satellite 6.2. (BZ#1551674)
- Restarting a pulp worker with running tasks caused the tasks to be in a broken state. This problem has been fixed. In such cases, tasks are stopped with warning "Task cancelled". This fix has been backported to Satellite 6.2. (BZ#1526437)
- Synchronization tasks that were interrupted by Satellite restarting were not completing. This is now fixed and has been backported to Satellite 6.2. (BZ#1548167)
- The foreman-debug tool has been updated to collect the foreman-maintain logs. This improves the ability to analyze problems during upgrades. (BZ#1542407)
- The katello-backup tool can now use relative paths. (BZ#1544396)
- Users received errors when they created hosts using hammer with two network interfaces if eth0 was not the primary interface. This is now fixed. (BZ#1417053)
- Users were not able to manage their own taxonomies. This functionality has been enabled. (BZ#1476843)
- Custom products created for RHEL5 were not using the correct checksum type. SHA1 is now used for these repositories. (BZ#1480694)
Users of Red Hat Satellite are advised to upgrade to these updated packages, which fix these bugs.
Satellite Migration from RHEL 6 to RHEL 7
As a reminder, Red Hat continues to strongly recommend your Satellite and Capsule Servers only be run on RHEL 7. There are several reasons why you should move your Satellite environment from RHEL 6 to RHEL 7 including enhanced performance and long-term supportability.
Future releases of Satellite (6.3 and above) will only support RHEL 7 and above.
In preparation for newer versions of Satellite, you need to start thinking about how to move from older versions of RHEL to RHEL 7.
While RHEL 6 does support an in-place migration from RHEL 6 to RHEL 7, this migration mechanism is not supported when running Satellite on the RHEL host. Instead, you will need to clone your Satellite environment from a host running RHEL 6 to another host running RHEL 7.
Review the Satellite 6.2.13 release blog for more detailed information about moving your Satellite environment from RHEL 6 to RHEL 7. 6.2.13 includes some important features for capsule backup and recovery which helps to ease the movement from RHEL 6 to RHEL 7.
Curios, I'm sure I can search for this, but if we are currently at 6.2.14 do all of the Capsules need to be upgraded at the same time? Or can they be caught up soon afterwords.?
Eleven capsules and growing, makes for a long evening ...
Hi Chris,the upgrade guide for Capsule Servers says:
6.5 - Before you begin
-You should have upgraded the Satellite Server before upgrading any Capsule Servers.
-The capsule should be on at least the 6.1.9 minor version of Red Hat Satellite Server 6.1. The requirement is to be at least on 6.1.9, upgrading to a higher minor version past 6.1.9 is not needed for the upgrade to Red Hat Satellite 6.2. Direct upgrades from earlier minor versions are not supported. For more information, see Upgrading Between Minor Versions of Satellite in the Red Hat Satellite 6.1 Installation Guide.
The conclusion for me is, that you can use older versions of capsules with a newer version of satellite server. Otherwise, there wouldn't be an upgrade procedure possible if you have for example more than 2 or 3 or in youre case 11 capsules. (I know customers with 100 and more)
It's not official, but practicaly I had no problems with older capsules f.e. 6.2.12 on a 6.2.15 satellite. But the gap between minor versions shouldn't be that big. If you have any doubts, open a case and ask the support, to be sure.
Best Regards Daniel