Product notes, new features, and known bugs for Red Hat Satellite.
Chapter 1. Introduction
Red Hat Satellite is a system management solution that enables you to deploy, configure, and maintain your systems across physical, virtual, and cloud environments. Satellite provides provisioning, remote management and monitoring of multiple Red Hat Enterprise Linux deployments with a single, centralized tool.
Red Hat Satellite Server synchronizes the content from Red Hat Customer Portal and other sources, and provides functionality including fine-grained life cycle management, user and group role-based access control, integrated subscription management, as well as advanced GUI, CLI, or API access.
Red Hat Satellite Capsule Server mirrors content from Red Hat Satellite Server to facilitate content federation across various geographical locations. Host systems can pull content and configuration from the Capsule Server in their location and not from the central Satellite Server. The Capsule Server also provides localized services such as Puppet Master, DHCP, DNS, or TFTP. Capsule Servers assist you in scaling Red Hat Satellite as the number of managed systems increases in your environment.
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.
Chapter 2. Content Delivery Network Repositories
This section describes the repositories required to install Red Hat Satellite 6.6.
You can install Red Hat Satellite 6.6 through the Content Delivery Network (CDN). To do so, configure
subscription-manager to use the correct repository for your operating system version and variant.
Run the following command to enable a CDN repository:
# subscription-manager repos --enable=reponame
Run the following command to disable a CDN repository:
# subscription-manager repos --disable=reponame
The following sections outline the repositories required by Red Hat Satellite 6.6. When one of these repositories is required to install a package, the steps to enable the required repositories are included in the documentation.
2.1. Red Hat Satellite
The following table lists the repositories for Red Hat Satellite Server.
Table 2.1. Red Hat Satellite
|Repository Name||Repository Label|
Red Hat Satellite 6.6 (for RHEL 7 Server) (RPMs)
Red Hat Satellite 6.6 (for RHEL 7 Server) (ISOs)
2.2. Red Hat Satellite Capsule
The following table lists the repositories for Red Hat Satellite Capsule Server.
Table 2.2. Red Hat Satellite Capsule
|Repository Name||Repository Label|
Red Hat Satellite Capsule 6.6 (for RHEL 7 Server) (RPMs)
2.3. Red Hat Satellite Maintenance
The following table lists the repositories for Red Hat Satellite Maintenance.
Table 2.3. Red Hat Satellite Maintenance
|Repository Name||Repository Label|
Red Hat Satellite Maintenance 6 (for RHEL 7 Server) (RPMs)
2.4. Red Hat Satellite Tools
The following tables list the repositories for Red Hat Satellite Tools.
Table 2.4. Red Hat Satellite Tools for Red Hat Enterprise Linux 5
|Repository Name||Repository Label|
Red Hat Satellite Tools 6.6 (for RHEL 5 Server -AUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 5 Server - ELS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 5 for System Z - ELS) (RPMs)
Table 2.5. Red Hat Satellite Tools for Red Hat Enterprise Linux 6
|Repository Name||Repository Label|
Red Hat Satellite Tools 6.6 (for RHEL 6 Desktop) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 Server) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 Server - AUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 Workstation) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 for System Z (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 for IBM Power) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 6 for Scientific Computing (RPMs)
Table 2.6. Red Hat Satellite Tools for Red Hat Enterprise Linux 7
|Repository Name||Repository Label|
Red Hat Satellite Tools 6.6 (for RHEL 7 Desktop) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Server) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Server - EUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Server - TUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Server - AUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Server - E4S) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 Workstation) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for System Z) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for System Z - EUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for IBM Power) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for IBM Power - EUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for IBM Power LE) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for IBM Power LE - EUS) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for IBM Power LE - E4S) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for Scientific Computing) (RPMs)
Red Hat Satellite Tools 6.6 (for RHEL 7 for Scientific Computing - EUS) (RPMs)
Table 2.7. Red Hat Satellite Tools for Red Hat Enterprise Linux 8
|Repository Name||Repository Label|
Red Hat Satellite Tools 6.6 for RHEL 8 x86_64 (RPMs)
Red Hat Satellite Tools 6.6 for RHEL 8 s390x (RPMs)
Red Hat Satellite Tools 6.6 for RHEL 8 ppc64le (RPMs)
Red Hat Satellite Tools 6.6 for RHEL 8 aarch64 (RPMs)
Chapter 3. Key Changes to the Documentation
Several notable changes have been made to the Red Hat Satellite documentation for this release. The following list outlines and explains these changes.
- Direct Documentation Feedback
To improve documentation quality and to collect feedback from customers, Direct Documentation Feedback (DDF) has been enabled for the multi-page HTML version of Satellite 6.5 and 6.6 English documentation.
To provide feedback on Satellite 6.5 or 6.6 documentation, you can click the Feedback button in the upper-right corner. You can also highlight text and click the Add Feedback button to comment on the documentation. Comments remain visible and a Bugzilla ticket that includes a copy of the comment is sent to the Red Hat Satellite documentation team for review.
- Administering Red Hat Satellite
The OpenSCAP documentation has been improved:
- Content Management Guide
The Provisioning Containers section has been removed from the Provisioning Guide, as it is no longer possible to provision containers in Red Hat Satellite 6.6. Information about managing container images is now in the Content Management Guide:
- Hammer CLI Guide
The Hammer CLI Guide now contains only Hammer CLI-related topics:
All the CLI procedures and Bash scripts related to using Satellite Server are now in the corresponding procedures in other guides.
- Managing Hosts
The Managing Hosts chapter of the Managing Hosts guide has been replaced with smaller, more specific chapters, such as Administering Hosts and Registering Hosts:
The documentation about using Red Hat Insights to monitor hosts in Satellite has been improved and moved from the Administering Red Hat Satellite guide to the Managing Hosts guide:
- Provisioning Guide
The Provisioning Guide now includes information about using the new
userdatatemplates with VMware:
- Installing Satellite Server
The Configuring Satellite Server with a Custom Server Certificate section of the Installing Satellite Server from a Connected Network and Installing Satellite Server from a Disconnected Network guides has been improved.
Configuring Satellite Server with a Custom Server Certificate in the Installing Satellite Server from a Connected Network guide
Configuring Satellite Server with a Custom Server Certificate in the Installing Satellite Server from a Disconnected Network guide
The documentation about using Red Hat Insights to monitor Satellite Server has been updated and moved from the Administering Red Hat Satellite guide to the Installing Satellite Server from a Connected Network guide.
- Installing Capsule Server
The Configuring Capsule Server with SSL Certificates chapter in the Installing Capsule Server guide has been created and includes improved instructions on configuring Capsule Server with default and custom SSL certificates:
- API Guide
- The Knowledgebase article API Changes Between Satellite Versions has been published to the Customer Portal and references to this article have been added to the API and Upgrading and Updating Red Hat Satellite guides.
Chapter 4. New Features and Enhancements
This chapter introduces new features in Red Hat Satellite 6.6.
- SWID passthrough
- When repositories contain SWID data, Red Hat Satellite 6.6 mirrors this data and persists it across all Content Views even when filtering.
- Warnings for
yumtransactions when upgrading
When updating or upgrading with
satellite-maintain, you are now warned before a
yumtransaction runs, and can cancel the action to take appropriate steps, if required.
satellite-maintainalias has been added for the
- Bypass exclusion when upgrading
When excluding packages from
yumupdates, if any of the excluded packages are from required Satellite repositories the
yumupdate can fail with dependency issues. To avoid this issue,
satellite-maintaincan now bypass exclusion when running the
yumupdate, to avoid cases when exclusion was configured and forgotten.
- Support for Ansible 2.8
- Red Hat Satellite 6.6 supports Ansible version 2.8. Ansible 2.6 reaches its end-of-life (EOL) in 2019.
- Support for Ansible variables
- Ansible variables are now supported on a similar level as smart class parameters for Puppet. Ansible manifests are scanned to determine what variables are available and allow you to import them. The Ansible variables can then be adjusted (for example, to set the correct type) and overwritten in the same way as for Puppet.
- Order of Precedence for Ansible variables
In previous versions of Satellite, the Ansible Keyword
become_userwas used to escalate Ansible roles to the
Effective Userwhen a user required elevated privileges such as overriding Ansible variables. Satellite 6.6 supports the Ansible variable order of precedence for overriding variables. If you have existing Ansible roles that use the Ansible Keyword
become_userto escalate user privilege and override variables, you must reconfigure these roles to follow the order of precedence. For more information, see Variable precedence: Where should I put a variable? in the Ansible User Guide.
- Support for Ansible Runner
In Red Hat Satellite 6.6 you can set Ansible Runner as the default method for running Ansible jobs, instead of calling
ansible-playbookdirectly. Ansible Runner is the recommended way to run Ansible jobs.
- OpenSCAP deployment using Ansible
- Previously you could not deploy OpenSCAP without Puppet. Red Hat Satellite 6.6 now supports deploying OpenSCAP with Ansible and reporting on hosts without using Puppet.
- Resolved a
Previously, when sending a
virt-whoreport to Satellite a short time after a previous one (even from a different set of hypervisors), Satellite’s task would fail on
undefined method '' for nil:NilClass. This issue has now been resolved.
virt-whoconfiguration plug-in enhancements
Red Hat Satellite 6.6 provides simpler and less error-prone configuration of
virt-whowith the following additional settings:
- You can now set shorter intervals than one hour (for example: 1 minute VIRTWHO_INTERVAL) through a configurable option.
virt-who-configure-pluginnow sets ‘NO_PROXY=*’ by default, which allows Satellite to successfully reach the Content Delivery Network.
- Support for Red Hat Virtualization version 4 API
- Red Hat Virtualization version 4 API integration was added in Satellite 6.4 as a Technology Preview. It is now fully supported in Red Hat Satellite 6.6.
- New task dashboard
- Red Hat Satellite 6.6 provides a task page that includes a dashboard with an emphasis on paused tasks and tasks with errors or warnings. This provides a better graphical status of the tasks.
- Task notification enhancements
Red Hat Satellite 6.6 includes the following enhancements when a paused task occurs in the system:
In the web UI, the
adminuser receives a notification about the current number of paused tasks in the system, and can navigate directly from the notifications area to the list of paused tasks.
- In the web UI, the user that initiated the task receives a notification about the specific task being paused, and can navigate directly from the notifications area to the details of the task, and to the Red Hat Knowledgebase article for troubleshooting.
- In the web UI, the
- Task logging enhancements
- Red Hat Satellite 6.6 now logs better details about the state change of a task (for example, paused or stopped tasks), including the task ID, execution plan ID, new state, and result.
- All Satellite and Capsule Servers log to
For consistency, all Satellite Servers and Capsule Servers now log by default to
- Support for cloud-init
Red Hat Satellite 6.6 includes the
foreman-userdataplug-in that provides support for deployments using
- Creating Content Views with dependency resolution
- When creating a Content View filter, you can add or remove arbitrary packages and errata to or from a Content View. Dependency resolution is now completed on the resultant repositories.
- Default scale setting enhancements
Red Hat Satellite 6.6 includes the following enhancements to its default behavior:
Satellite now includes a set of predefined
custom-heira.yamltemplates for various memory and size configurations. These templates provide recommended pre-configured tuning settings that you can use instead of reading a tuning guide and making changes manually. For more information, see Tuning Satellite Server with Predefined Profiles in Installing Satellite Server from a Connected Network.
- The cleaning unused tasks feature is now enabled by default. This reduces performance issues, disk consumption, and increases success with upgrades. For more information, see Configuring the Cleaning Unused Tasks Feature in Administering Red Hat Satellite.
- Satellite now includes a set of predefined
- Reporting enhancements
Red Hat Satellite 6.6 includes the following enhancements to the reporting engine added in Satellite 6.5:
- A new applied errata reporting template
- The ability to schedule reports
- The ability to email reports
- Support for provisioning on Google Compute Engine
Red Hat Satellite 6.6 supports Google Compute Engine (GCE) as a provisioning platform, including the following features:
- Creating a GCE compute resource
- Image-based provisioning using that compute resource
- Sending updates from a Satellite Server on-premise using a VPN
Decommissioning GCE virtual machines
Support for the CLI and API will be added in a later release of Red Hat Satellite.
- Composer integration
- With Composer integration in Red Hat Satellite 6.6, you can download content from Satellite in order to build images for deployment. You can then upload the deployment images into Satellite and use Satellite to provision these images.
- Kickstart default provisioning template enhancements
The new option
fips_enabledis introduced, which ensures that FIPS-related packages are installed.
The kickstart statement
repocan be modified with the
%postsnippet error occurs, the error is reported in the host’s status in the Satellite web UI.
Kickstart default custom postsnippet is automatically added to the
%postsection of the template without the need to change the template itself.
- The new option
Chapter 5. 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.
This release of Red Hat Satellite 6 features the following enhancements:
BZ#1152515 You can configure a Content View to resolve package dependencies on publishing by navigating to a Content View and selecting the Solve Dependencies check box. You can configure two global settings for the dependency solving feature: 1. You can configure the dependency solving feature to be enabled or disabled by default by navigating to Administer > Settings > Content and changing the Content View Dependency Solving Default setting. 2. You can select the dependency solving algorithm that you want to apply by navigating to Administer > Settings > Content and changing the Content View Dependency Solving Algorithm setting. When the Solve Dependencies check box is selected for a Content View, Satellite checks repositories in the Content View for dependency conflicts and overwrites Content View filters to resolve existing conflicts. The dependency solving feature has three caveats: 1. Publishing a Content View with the dependency solving feature enabled takes approximately three times longer. 2. The dependency solving feature does not resolve dependency conflicts across repositories. 3. You must ensure that the Content View with the dependency solving feature enabled works correctly after publishing. Content Views still might have dependency conflicts in an errata workflow and when working with custom repositories.
BZ#1559006 In Red Hat Satellite 6.6, you can now select a destination storage domain when creating a host on Red Hat Virtualization. When selecting a template that includes disks for a host, you can change the storage domain and the storage allocation. This clones the disk from the template and changes the storage domain and allocation of the cloned disk, allowing you to select a destination storage domain without needing to manually clone the disk in Red Hat Virtualization first.
BZ#1658265 Previously, if you had an HTTP proxy configured in Satellite, the virt-who configuration attempted to use the HTTP proxy to submit virt-who data and failed. With this release, virt-who ignores the HTTP proxy setting and submits data to Satellite directly.
BZ#1684573 Ansible 2.8 is now supported.
BZ#1698148 Red Hat Satellite 6.6 now supports passing through SWID tag data when it is provided in a repository which is being synced.
BZ#1730648 Previously, Satellite created duplicated profiles for RHEL-based hypervisors causing them to consume twice as many subscriptions. Users had to configure virt-who in VDSM mode manually on RHEL-based hypervisors prior to registering them to Satellite. From Satellite 6.6 onwards, Satellite creates unique profiles for RHEL-based hypervisors. Therefore, you must first register RHEL-based hypervisors with subscription-manager and then configure virt-who using the virt-who configuration tool in the Satellite web UI.
BZ#1738199 Previously, using yum to update or install packages on the Satellite base operating system might have also updated the packages related to Satellite and resulted in system inconsistency. With this release, Satellite prevents users from installing and updating packages with
yum. Instead, you must use
foreman-maintain packages install and
foreman-maintain packages update commands. Note that
foreman-maintain runs the
satellite-installer --upgrade script after installing packages and therefore some services are restarted. You can disable this feature and control the stability of the system yourself if you want. This feature is not enabled on Capsule Server.
5.2. Technology Preview
The items listed in this section are provided as Technology Previews. For further information on the scope of Technology Preview status, and the associated support implications, see Technology Preview Features Support Scope.
- Container-native Virtualization Plug-in
- The Container-native Virtualization Plug-in is now available in Satellite 6.6 as a Technology Preview feature.
- Kernel Execution (
- The Kernel execution template for PXE-less boot methods, which was introduced in Satellite 6.2, continues to be available as a Technology Preview feature.
- Integration with the Tracer tool, which was introduced in Satellite 6.3, continues to be available as a Technology Preview feature.
5.3. 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#1612800 For VMware hypervisors, you can now filter and exclude host parents through the Satellite web UI, API, and Hammer CLI.
BZ#1658284 Three new intervals for the virt-who configuration have been added: 24 hours, 2 days, and 3 days. You can now configure Satellite to run the virt-who at the following intervals: every hour, every 2 hours, every 4 hours, every 8 hours, every 12 hours, every 24 hours, every 2 days, or every 3 days.
5.4. Known Issues
These known issues exist in Red Hat Satellite 6 at this time:
BZ#1578911 When you provision a host using the VMware compute resource, you can only select the default resource pool. If you try to select a different resource pool, provisioning fails. As a workaround, disable the cache on the compute resource.
BZ#1649927 Using the Hammer CLI, there are problems provisioning from an image using the VMware compute resource. As a workaround, specify the image_id in the --compute-attributes option in the Hammer CLI, for example, --compute-attributes="image_id='500d7545-8e17-ce0f-4011-79c5c2c88e49'.
BZ#1678179 In the Satellite web UI, the bulk action feature for the set repositories of content hosts does not list the custom product repositories. An empty list is displayed rather than a list of the custom repositories.
BZ#1686245 If you download Kickstart repositories with an "On Demand" policy, Satellite stores the files incorrectly and this causes problems during provisioning. Use only the "Immediate" policy for Kickstart repositories.
BZ#1692753 The description of the location_id and organization_id parameters are unclear in the ApiDoc and the error message for these parameters is incorrect. You must use these parameters to set the context scope for an API query, but not to update a location or organization of a compute resource. If you use this command to update a compute resource, an API request returns the wrong error message "Compute resource doesn’t exist".
BZ#1713401 When you apply the OSPP security policy to a Red Hat Enterprise Linux 8 system during provisioning, the katello-ca-consumer package cannot be installed from Satellite Server. Therefore, the system cannot be registered as a content host. As a workaround, after the system is provisioned, install the katello-ca-consumer with the following command and then register the system manually: # rpm -Uvh --nodigest --nofiledigest http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
BZ#1719175 If an HTTP proxy password contains special characters, such as "?", Insights uploads fail with the "407 Proxy Authentication Required" error. Do not use special characters in an HTTP proxy password.
BZ#1719636 If you edit the subscription information for hosts in Satellite, the hosts do not display in the audit records of the Satellite web UI. Instead of a list of hosts, the following error is displayed: "Missing(ID: 2)" in "Host ids" line.
BZ#1720369 Entering the following command can lead to broken symlinks for repository metadata. Do not enter this command until BZ#1720369 is resolved. # foreman-rake katello:delete_orphaned_content RAILS_ENV=production If you have broken symlinks, regenerate the yum repository metadata.
BZ#1728612 Ansible jobs always use the sudo become_method. If you change the Effective User Method, the changed setting only affects SSH remote execution jobs, not Ansible jobs.
BZ#1732657 Client registration with subscription-manager in Satellite 6.5 and later is slower than in previous versions, because of additional audit and facts data being stored during registration.
BZ#1743706 Satellite Server operating in FIPS mode cannot connect to an external MongoDB server. To use FIPS mode and MongoDB, use the internal MongoDB.
hammer organization command shows a warning for deprecated options even when those options are not used. The command still works without issue; if you are not using the deprecated options you can ignore the warnings.
BZ#1745835 Full Capsule synchronization fails and does not fully publish new metadata.
BZ#1750239 If you attach subscriptions to hosts during registration using activation keys, Satellite attaches subscriptions incorrectly. Instead, use auto-attach.
BZ#1750248 Rotated log files are not reopened even when a HUP signal is sent to the foreman-proxy daemon. As a result, deleted files are reported as still open, logging does not work correctly, and log records can be lost. You can check for deleted files by running the following command: lsof | grep deleted | grep "\/var\/log" To work around this issue, restart the foreman-proxy service after logs are rotated.
BZ#1754314 Satellite hosts that use katello-agent might experience a memory leak caused by the qpid-proton package.
BZ#1754881 Foreman-maintain fails to restore data from some backups due to issues reading tar files. In a future release, foreman-maintain will be updated to use GNU tar to support all tar archive edge cases.
BZ#1758645 You cannot provision a VMWare virtual machine with the ESXi 6.7 U2 hardware version from Satellite.
BZ#1759021 The documentation button in Hosts → Content Hosts → Register Content Host returns a 404 error. The URL changed but was not updated in the Satellite web UI. To access the correct document, navigate to https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html/managing_hosts/registering_hosts manually.
foreman-maintain packages update all command does not work. To update all packages on the Satellite base operating system, enter the
foreman-maintain packages update \\* command.
5.5. Deprecated Functionality
The items in this section are either no longer supported or will no longer be supported in a future release.
BZ#1670092 In Red Hat Satellite 6.6, the "hammer csv" command for importing or exporting resources has been removed. You can still use the "hammer --csv" command to generate formatted output only.
BZ#1698182 In Red Hat Satellite 6.6, the foreman_docker plug-in has been removed, therefore it is no longer possible to provision containers.
--environment-id options of the
hammer command are deprecated because of confusion between lifecycle and Puppet environments. Use the
--puppet-environment options instead.
BZ#1716615 Subscription Events for content hosts (Hosts > Content Hosts > Host name > Subscriptions > Events in the Satellite web UI) are deprecated and will be removed in a future release.
BZ#1741454 Both foreman_organization and foreman_location fact values were deprecated for discovery, use discovery_organization or discovery_location fact values instead. Ensure that the subnet in which the discovered node is detected also belongs to the organization and location set by the fact, otherwise Satellite refuses to set it for security reasons.