Release Notes

Red Hat Satellite 6.2

Product notes, new features, and known bugs for Red Hat Satellite 6.2.

Edition 1

Red Hat Satellite Documentation Team

Abstract

This document contains product notes, brief descriptions of new features, and known bugs for Red Hat Satellite 6.2.

Chapter 1. Introduction

Red Hat Satellite 6 is the evolution of Red Hat's life cycle management platform. It provides the capabilities that administrators have come to expect in a tool focused on managing systems and content for a global enterprise. Satellite 6 covers the use cases requested by Satellite 5 customers, but also includes functionality that enables larger scale, federation of content, better control of systems during the provisioning process, and a much more simplified approach to life cycle management. Satellite 6 also further evolves the inherent approach to certificate-based entitlements and integrated subscription management. Satellite 6 is based on years of customer feedback and is an evolution of previous versions.

1.1. Satellite 6 Component Versions

Red Hat Satellite is a combination of a number of upstream projects. For the full details of the major projects included, and the version of those projects included in each major and minor release of Red Hat Satellite, see Satellite 6 Component Versions.

1.2. Red Hat Satellite and Proxy Server Life Cycle

For an overview of the life cycle phases for Red Hat Network Satellite and Red Hat Satellite and the status of support for these products, see Red Hat Satellite and Proxy Server Life Cycle.

1.3. Red Hat Satellite FAQ

For a list of frequently asked questions about Red Hat Satellite 6, see Red Hat Satellite 6 FAQ.

1.4. Content Delivery Network (CDN) Channels

This section describes the channel and repository settings required to deploy Red Hat Satellite 6.2.
You can install Red Hat Satellite 6.2 through the Content Delivery Network (CDN). To do so, configure subscription-manager to use the correct channels.
Run the following command to enable a CDN channel:
#subscription-manager repos --enable=[reponame]
Run the following command to disable a CDN channel:
#subscription-manager repos --disable=[reponame]

Table 1.1.  Red Hat Enterprise Linux 6

Channel Repository Name
Red Hat Enterprise Linux 6 Server (RPMS) rhel-6-server-rpms
Red Hat Software Collections RPMs for Red Hat Enterprise Linux 6 Server rhel-server-rhscl-6-rpms
Red Hat Satellite 6.2 (for RHEL 6 Server) (RPMS) rhel-6-server-satellite-6.2-rpms
Red Hat Satellite Capsule 6.2 (for RHEL 6 Server) (RPMS) rhel-6-server-satellite-capsule-6.2-rpms

Table 1.2.  Red Hat Enterprise Linux 7

Channel Repository Name
Red Hat Enterprise Linux 7 Server (RPMS) rhel-7-server-rpms
Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server rhel-server-rhscl-7-rpms
Red Hat Satellite 6.2 (for RHEL 7 Server) (RPMS) rhel-7-server-satellite-6.2-rpms
Red Hat Satellite Capsule 6.2 (for RHEL 7 Server) (RPMS) rhel-7-server-satellite-capsule-6.2-rpms

Chapter 2. New Features and Enhancements

This chapter introduces new features in Red Hat Satellite 6.2, and links to further information.
Increase Efficiency with Automated Workflows

Satellite 6.2 introduces remote execution, automating workflows and enabling users to take multiple actions against groups of systems, such as rebooting a system after a patch install or conduct rolling upgrades across hundreds of systems as easily as one. Users can easily build a script library, share scripts and share repeatable workflows, enabling less experienced administrators to execute complex workflows. In addition, users can schedule tasks and use new dashboards for enhanced interaction with systems under management.

Increase Security in Disconnected Environments

Satellite 6.2 provides the ability to synchronize and export content from one Satellite to another, especially useful for organizations that require their systems management solution to run disconnected from the internet for security purposes.

More Flexible Provisioning

Discovery enhancements in Satellite simplify the process of building systems and allow end users to more efficiently provision systems in secured environments where DHCP and PXE may not be available.

Increased Reliability, Availability, and Serviceability

Satellite 6.2 includes a number performance enhancements, highlighted by the following:

Build systems during content synch
Streamlined content synchronization enables users to build systems almost immediately after install while content downloads in the background.
Faster backups
Satellite content synchronization speeds the backup and restore process because software packages are no longer required to be backed up. This drastically reduces the amount of time a Satellite needs to be offline for backup.
Capsule visibility
The Red Hat Satellite Capsule user interface provides much deeper insight into the health of the Capsule, such as what services are running and their status, from the centralized Satellite console.
Lighter-Weight Capsules
Red Hat Satellite repositories can be configured to store only the content that has been requested by clients. This reduces the storage needed. This feature is available as a Technology Preview in Satellite 6.2. For information on Red Hat Technology Preview features support scope, see Technology Preview Features Support Scope. Note that this feature is fully supported from release 6.2.3.
Ability to Import Existing Hosts

Satellite 6.2 features new scripts and automation to import existing Red Hat infrastructure hosts that may reside on any Red Hat systems management platform, including Red Hat Satellite 5.x. This bootstrap script automates the process of registering systems to Satellite, dramatically reducing the number of steps required to get existing systems ready to be managed by Red Hat Satellite.

Containers and the Container Host Infrastructure

The latest version of Red Hat Satellite includes RHEL Atomic Hosts support, enabling users to provision and manage RHEL Atomic Hosts, Red Hat’s hardened platform for container workloads. Red Hat Satellite also supports RHEL Atomic Hosts as a compute resource, allowing container deployments to RHEL Atomic Hosts. In addition, Red Hat Satellite now supports Docker v2 API and registries.

Chapter 3. Release Information

These release notes highlight technology preview items, recommended practices, known issues, and deprecated functionality to be taken into consideration when deploying this release of Red Hat Satellite 6.
Notes for updates released during the support lifecycle of this Red Hat Satellite 6 release will appear in the advisory text associated with each update.

3.1. Enhancements

This release of Red Hat Satellite 6 features the following enhancements:
BZ#1369107
Previously, the virt-who daemon recognized any file in the /etc/virt-who.d/ directory as a potential configuration file, regardless of extension. With the release of Red Hat Satellite 6.2.9 and virt-who version 0.19 and above, only files with the .conf extension are now recognized as potential configuration files. All configuration files without the .conf extension must be updated to include this extension.
BZ#1217527
Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.
BZ#1127456
This release introduces the ability to export content from one Satellite Server and import it into another server. The content can come from the Library, or can be from a content view. This feature can be used to support populating an air-gapped server with content from another server.
BZ#1209467
With this release, the virt-who agent can now be installed on the same machine where the main Satellite Server is hosted.
BZ#1052257
With this release, the default root password hash has been made SHA256 instead of MD5. This improves the default security of all provisioned hosts.
BZ#1131296
This release adds a Remote Execution feature that allows users to execute commands against machines under inventory. The commands can be stored as jobs, and can be scheduled to run in the future or on a recurring basis.
BZ#1144232
With this release, a "Test Connection" button was added to verify LDAP connection information.
BZ#1154373
A bootstrap script has been included with Red Hat Satellite 6.2. This script takes a machine that has been provisioned outside of Red Hat Satellite 6.2 and registers the host, installs the appropriate certificates, and configures puppet. If the host was previously registered with Red Ht Satellite 5, the script selects the correct subscriptions based on the channels that are assigned to the host.
BZ#1154383
The hammer command now supports defaults, which can be stored on the file system to make it easier to execute multiple hammer commands in a single session.
BZ#1146874
With this release, the content dashboard in Red Hat Satellite 6.1 has now been combined into the main dashboard, providing a single point of summary information for the user.
BZ#1174948
With this release, users of Red Hat Satellite 6.2 can sync down repositories protected by basic authentication by providing the username and password in the repository string.
BZ#1241975
With this release, content view versions in Red Hat Satellite 6.2 have been improved to show the version of the puppet module that is included.
BZ#1254413
With this release, the backup script has been updated to perform incremental backups of the raw packages. This speeds up all subsequent backups.
BZ#1268896
With this release, the backup script has been updated to allow for backing up database information. This option improves backup performance for users whose packages are stored on backed-up file systems.
BZ#1297834
As part of upgrading to the latest Puppet 3.x version, the hiera package has now been updated to 1.3.
BZ#1315043
This release introduces the ability to provision Red Hat Atomic Host in addition to standard Red Hat Enterprise Linux. This includes syncing down Atomic Content, promoting that content through a lifecycle environment, and provisioning Atomic Hosts.

3.2. Release Notes

This section outlines important details about the release, including recommended practices and notable changes to Red Hat Satellite. You must take this information into account to ensure the best possible outcomes for your deployment.
BZ#1348135
During a Satellite 6.2 upgrade, as part of the host unification feature, if a host and content host are found with the same name but within different organizations, the content host will be unregistered. This will remove the content host from the Satellite. Consequently, once the content host has been unregistered by the upgrade process, it is possible that errors will be observed in /var/log/foreman/production.log as the content host may still attempt to interact with the Satellite via Red Hat Subscription Manager (RHSM).

The errors can include ones similar to the following:

2016-06-20 04:02:30 [app] [E] RestClient::Unauthorized: Katello::Resources::Candlepin::Consumer: 401 Unauthorized {"displayMessage":"Invalid oauth unit or secret","requestUuid":"56562131-15b1-482b-86c3-a74da4b19491"} (GET /candlepin/consumers/c1d5c956-b9c5-4088-914b-fd5e0e828c32)

2016-06-20 04:22:23 [app] [E] RestClient::Gone: Katello::Resources::Candlepin::Consumer: 410 Gone {"displayMessage":"Unit c1d5c956-b9c5-4088-914b-fd5e0e828c32 has been deleted","requestUuid":"4d433cb8-e94a-49dc-9d2f-eebdc7066e55","deletedId":"c1d5c956-b9c5-4088-914b-fd5e0e828c32"} 

Workaround

Prior to performing the Satellite 6.2 upgrade, the user should execute the pre-upgrade script on the Satellite 6.1 Server to obtain a summary of the content hosts that will be unregistered. The script may be executed as:

foreman-rake katello:upgrade_check

Prior to the upgrade, the user should then update the hosts and content hosts to ensure that they are in the correct organizations. If this is not done prior to the upgrade, the user will need to re-register each of those content hosts using the Red Hat Subscription Manager command-line tool after the upgrade has completed.
BZ#1357158
In Satellite 6.2, Docker support has been upgraded from Docker v1 to v2. With this change, Docker has made fundamental changes in its data model to move from supporting Docker Images to supporting Docker Manifests. Due to the significance of this change, any existing Docker v1 repositories will be removed from the Satellite during the upgrade process.
BZ#1344215
During a Satellite 6.2 upgrade, as part of the host unification feature, if a host and content host are found with same name but within different organizations, the content host will be unregistered. This will remove the content host from the Satellite. Consequently, once the content host has been unregistered by the upgrade process, it is possible that errors will be observed in /var/log/messages as the content host may still attempt to interact with the Satellite via the agent.

The errors can include ones similar to the following:

[Protocol] error Error on attach: Node not found: pulp.agent.737d5dde-2ec8-4b21-9933-3e7fa45cbf77

Workaround

Prior to performing the Satellite 6.2 upgrade, the user should execute the pre-upgrade script on the Satellite 6.1 Server to obtain a summary of the content hosts that will be unregistered. The script may be executed as:

foreman-rake katello:upgrade_check

Prior to the upgrade, the user should then update the hosts and content hosts to ensure that they are in the correct organizations. If this is not done prior to the upgrade, the user will need to re-register each of those content hosts using the Red Hat Subscription Manager command-line tool after the upgrade has completed.

3.3. Known Issues

These known issues exist in Red Hat Satellite 6 at this time:
BZ#1305591
The command katello-disconnected has been removed. You should perform a complete satellite installation and use Inter Satellite Sync to move content across air-gapped networks.
BZ#1365820
Rails events no longer triggering hooks in /hooks/report

In Satellite 6.2 the Report class is changed to ConfigReport so the hooks are no longer looking for a script stored in the /hooks/report/ directory.

Create a directory /usr/share/foreman/config/hooks/config_report/ and move hooks such as `after_create` and `before_create` to the new directory.
BZ#1346654
Currently, Red Hat Enterprise Linux 6.4 AUS and 6.2 AUS are not supported. You must use packages from later releases to manage machines using these AUS versions.
BZ#1432013
Using the katello-backup script with the --online-backup option requires a directory writable by the postgres user. Until this Red Hat Bugzilla is resolved, use only the /tmp directory to create online backups.

3.4. Deprecated Functionality

The items in this section are either no longer supported or will no longer be supported in a future release
BZ#1390042
The 'has_primary_interface?' method has been deprecated, so any attempt to use it results in the error "undefined method" being thrown. In Red Hat Satellite 6.2, each host automatically gets a primary interface when it is created, so this method is no longer required. Instead, the following tests whether the interface has an identifier:

host.primary_interface.identifier.empty?

The whole network interface object is available via the method: host.primary_interface.
BZ#1315286
The gutterball engine has been removed from Red Hat Satellite 6.2. The data stored in gutterball was never used.
BZ#1259374
Elastic Search has been removed from Red Hat Satellite. It has been replaced by the standard searching provided by the database.

Legal Notice

Copyright © 2016 Red Hat.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.