Warning message

Log in to add comments.

Satellite 6.3.2 is now available

John Spinks published on 2018-06-20T07:04:16+00:00, last updated 2018-06-23T21:16:57+00:00

Satellite 6.3.2 has just been released.
The main driver for the 6.3.2 release is allowing customers to disable weak ciphers, but there are several other new features and fixes.
There are two errata for the server [1][3] and one
for the hosts [2]. The install ISOs will be updated later this week.

Customers who have already upgraded to Satellite 6.3 should follow the instructions in the errata.
Customers who are on older versions of Satellite should refer to the Upgrading and Updating Red Hat Satellite Guide.

You may also want to consider using the Satellite Upgrade Helper if moving from Satellite 6.x to Satellite 6.3

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.

This update fixes the following bugs:

  • Users can now disable weak ciphers across Satellite 6's series of
    services and restrict to only TLS 1.2. For more information, see How to
    disable weak encryption (SSL 2.0 and SSL 3.0) on Red Hat Satellite:
    https://access.redhat.com/solutions/26833 (BZ#1553875, BZ#1318973)

    NOTE: If you are still using RHEL 5 Servers note that restricting communications to only TLS 1.2 will prevent RHEL5 from communicating with Satellite. Refer to Known Issues and Attacks Against SSL/TLS in OpenSSL/NSS/gnutls on Red Hat Enterprise Linux 5 for full details about supported TLS versions with RHEL 5.

  • The foreman-debug command now collects additional information to help
    with debugging, including passenger statistics. (BZ#1540493, BZ#1558545)

  • Satellite 6.3 could not sync containers from the Google or Quay
    registry because of differences in version 2 of the API. Satellite now
    supports these differences. (BZ#1555165)

  • Performance improvements, which arose from experiences with customer
    upgrades, are now available for the UI and CLI. (BZ#1511503, BZ#1567978,
    BZ#1553263, BZ#1560740, BZ#1563002, BZ#1575113)

  • Certain future-dated subscriptions could not be enabled based on the
    products they enable. This is now fixed. (BZ#1553264)

  • Authentication for OpenStack v3 was failing because Satellite did not
    use the domain field. This is now fixed. (BZ#1513932)

  • Problems that relate to migrating and upgrading, for example the
    content_source_id not migrating and template history disappearing, are
    now fixed. (BZ#1584874, BZ#1559108)

  • Intermittent segmentation faults in the Pulp stack are now fixed.
    (BZ#1516481)

  • Provisioning templates in RHEV 3.6 ignored the disk settings specified
    in the template. This is now fixed. (BZ#1399102)

  • The boot disk provisioning option was omitted from the hammer host
    create command. This is now fixed. (BZ#1544498)

  • Remote execution failed on host collections. This is now fixed.
    (BZ#1553017)

  • Intermittent segmentation faults in the qpid stack are now fixed.
    (BZ#1561819)

  • The initial remote execution command after a restart failed with the
    error message: "Could not use any Capsule". This is now fixed. (BZ#1558069)

  • Pulp workers became deadlocked when the PULP_MAX_TASKS_PER_CHILD setting was enabled. These workers now reconnect correctly. (BZ#1590906)

[1] https://access.redhat.com/errata/RHBA-2018:1950

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

[3]https://access.redhat.com/errata/RHBA-2018:1956

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.