Satellite 6.2.4 has been released today. 6.2.4 introduces many performance and stability improvements. There are two errata, one for the server  and one for the clients .
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 at .
Previously released (which we did not post a blog post for) was Satellite 6.2.3, which included a number of fixes [, and a new feature: Lazy Sync
Lazy Sync provides additional flexibility in how Satellite & Satellite Capsule synchronize and manage content. The primary advantages that Lazy Sync provides is that:
- It is no longer required to completely synchronize a repo prior to using it (either directly or as part of a content view)
- disk space usage for Satellite and Capsules can be reduced.
Details on Lazy Sync can be found in Satellite 6.2 Feature Overview: Lazy Sync
The list of bugs in 6.2.4 are:
Uploading a manifest for a second organization was failing due to duplicate content IDs. An unnecessary unique index was removed to support this case. (BZ#1388201)
Large virt-who checkins were causing performance issues. The json is no longer stored, removing the issue. (BZ#1369082)
- Performance improvements have been made to the dashboard. (BZ#1384199, BZ#1374038)
- Performance improvements have been made to the installation and upgrade process. (BZ#1264597, BZ#1381702)
- The performance of errata applicability has been improved. (BZ#1387314)
- The performance of free-form text searching has been improved. (BZ#1380486)
- Several memory leaks have been fixed in the qpid dispatch router. (BZ#1340375, BZ#1366232, BZ#1353458, BZ#1367735)
- Virt-who checkins will now use the default organization if the hypervisor is not associated to an organization. (BZ#1357878)
Please reach out with any questions or concerns.