Warning message

Log in to add comments.

Satellite 6.2.14 is now available

John Spinks published on 2018-02-05T15:43:11+00:00, last updated 2018-02-19T14:38:48+00:00

Red Hat Satellite 6.2.14 includes fixes for performance improvements and stability, as well as upgrade enhancements to make it easier to upgrade Satellite 6.2 to the upcoming Satellite 6.3 release.
There is one erratum for the server [1] and one for the hosts [2]. The install ISOs will be updated later this 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.14

Security Fixes:

  • It was discovered that python-twisted-web used the value of the Proxy header from HTTP requests to initialize the HTTP_PROXY environment variable for CGI scripts, which in turn was incorrectly used by certain HTTP client implementations to configure the proxy for outgoing HTTP requests. A remote attacker could possibly use this flaw to redirect HTTP requests performed by a CGI script to an attacker-controlled proxy via a malicious HTTP request. (CVE-2016-1000111)

Bugs:

  • Upgrades from Satellite 6.2 to Satellite 6.3 were failing due to the use of certificates with custom authorities. These upgrade paths now work. (BZ#1523880, BZ#1527963)
  • Additional tooling is provided to support data validation when upgrading from Satellite 6.2 to Satellite 6.3. (BZ#1519904)
  • Several memory usage bugs in goferd and qpid have been resolved. (BZ#1319165, BZ#1318015, BZ#1492355, BZ#1491160, BZ#1440235)
  • The performance of Puppet reporting and errata applicability has been improved. (BZ#1465146, BZ#1482204)
  • Upgrading from 6.2.10 to 6.2.11 without correctly stopping services can cause the upgrade to fail on removing qpid data. This case is now handled properly. (BZ#1482539)
  • The cipher suites for the Puppet server can now be configured by the installation process. (BZ#1491363)
  • The default cipher suite for the Apache server is now more secure by default. (BZ#1467434)
  • The Pulp server contained in Satellite has been enhanced to better handle concurrent processing of errata applicability for a single host and syncing Puppet repositories. (BZ#1515195, BZ#1421594)
  • VDC subscriptions create guest pools which are for a single host only. Administrators were attaching these pools to activation keys which was incorrect. The ability to do this has been disabled. (BZ#1369189)
  • Satellite was not susceptible to RHSA-2016:1978 but security scanners would incorrectly flag this as an issue. The package from this errata is now delivered in the Satellite channel to avoid these false positives. (BZ#1497337)
  • OpenScap report parsing resulted in a memory leak. This leak has been fixed. (BZ#1454743)
  • The validation on the length of names for docker containers and repositories was too restrictive. Names can now be longer. (BZ#1424689)
  • Goferd continues to leak memory when qdrouterd is not accessible. Was supposedly fixed as per bz 1260963 (BZ#1318015)

Users of Red Hat Satellite are advised to upgrade to these updated packages, which fix these bugs.

[1] https://access.redhat.com/errata/RHSA-2018:0273

[2] https://access.redhat.com/errata/RHBA-2018:0272

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.

English

About The Author

John Spinks's picture Red Hat

John Spinks

John Spinks is a Principal Technical Marketing Manager for Red Hat. He acts as a subject matter expert for Red Hat Satellite and works with Red Hat partners and customers to build and share relevant information about managing patching, provisioning, subscription, and configuration management for Re...
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.