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.

5.1. Enhancements

This release of Red Hat Satellite 6 features the following enhancements:


Previously, users had to synchronize the Atomic Kickstart Tree content manually through a custom repository. With this release, users can synchronize the Atomic Kickstart Tree content from within the Red Hat Content Delivery Network.

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

Synchronize Templates from Git Repositories
Satellite 6.3 introduces a plug-in that allows templates to be pushed to, and pulled from, an external Git repository or filesystem. For more information, see Synchronizing Templates with Git.
Auto-attach Bootdisk for VMWare
Satellite 6.3 introduces an auto-attach bootdisk for VMWare as a feature. For more information, see Satellite 6.3 Feature Overview: Auto-attach Bootdisk for VMWare [Tech Preview].
Satellite 6.3 introduces Tracer, an integration with the Tracer tool that monitors running processes and identifies if they need to be restarted due to package updates or similar activities. For more information, see Satellite 6.3 Feature Overview: Tracer [Tech Preview].


Previously, provisioning on IBM POWER was not available. With this release, provisioning clients on IBM POWER via BOOTP is 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.


Previously, there was an API JSON field named "enabled_override" for the API at "/api/v2/hosts/1/subscriptions/product_content". With this release, the API JSON field name "enabled_override" has been deprecated in favor of "override" to improve consistency.


To synchronize container images from a registry with self-signed certificates, you must either configure certificates manually or disable the SSL Verify option.


With this release, the roles included in Red Hat Satellite are now read only. If any of these roles were previously customized, an editable version of those roles with the name "Cuztomized XXXX" is created when you upgrade your environment to this version.


Because of security fixes that were introduced with this fix, if you clone templates that contain Ruby's `to-proc` syntax in Satellite 6.2, and then upgrade to Satellite 6.3, you cannot use the template.

As a workaround, write the same code as a full Ruby block, for example, `(1..3).collect(&:to_s)` becomes `(1..3).collect {|num| num.to_s}`.

To find affected code, search the template for `&:`. Replace `…(&:…)` with `…{|i| i.…}`.

Use the following two examples as a guide:

Ruby syntax in 6.2 cloned template:

 <% host_param('ssh_authorized_keys').split(',').map(&:strip).each do |ssh_key| -%>

Updated Ruby syntax for Satellite 6.3:

 <% host_param('ssh_authorized_keys').split(',').map{ |item| item.strip }.each do |ssh_key| -%>

Ruby syntax in 6.2 cloned template:

 nameserver=#{[subnet.dns_primary, subnet.dns_secondary].select(&:present?).join(',')}

Updated Ruby syntax for Satellite 6.3:

 nameserver=#{[subnet.dns_primary, subnet.dns_secondary].select{ |item| item.present? }.join(',')}


Previously, the templates used "<%= foreman_url %>" to notify Satellite that the build is done. In 6.3, the templates use "<%= foreman_url('built') %>", which explicitly calls the 'built' template.


If you plan to manually upgrade from Satellite 6.2 to Satellite 6.3, and if you previously installed the python-pulp-agent-lib package, you must enable the satellite-tools repository to successfully perform the upgrade. This package was moved into the tools repository for Satellite 6.3.


Several parameters of the capsule-certs-generate command were changed, and some were added. Those prefixed --capsule were changed to a --foreman-proxy prefix. New parameters prefixed --reset were added to allow commonly-used parameters to be reset to their default values. A --certs-reset parameter was added to reset any custom certificates and use the self-signed CA instead.

5.4. Deprecated Functionality

Subscriptions Manager Registration Snippet

In this release, you can no longer use the subscription_manager_registration snippet in a template to enable Satellite Tools repositories. You must configure your repositories to be enabled using an activation key.

Hammer Import Tool

In this release, you can no longer use hammer import functionality. To import hosts, you can use the bootstrap script For more information, see Importing Existing Hosts via the Bootstrap Script.

5.5. Known Issues

These known issues exist in Red Hat Satellite 6 at this time.


Known Issue
Hosts provisioned by Satellite, but not registered, are showing a green icon, indicating they are covered by a subscription. These should show a red icon, indicating they are not covered by a subscription.


Known Issue
In the Red Hat Subscriptions tab of the user interface, the hyperlinks used in the subscription type "Guests of hypervisor-name" are incorrect and broken. This is due to the hyperlink using the candlepin uuid rather than the host ID.


Known Issue

On Puppet Forge, some Puppet modules are invalid and cannot sync with Satellite.

These invalid Puppet modules cause error messages such as Invalid properties or MissingModulePile.

Despite receiving a report of a sync failure, the valid Puppet modules sync from Puppet Forge into Satellite.


Known Issue
Satellite Installer requires absolute paths. Always provide an absolute path for --certs-tar. For example, /root/ If you run the installer with a relative path, run the installer again with the absolute path and the --scenario parameter to create the last_scenario.yml.


Known Issue
The command katello-change-hostname creates an error condition when run on Satellite 6.2 during migration and upgrade. This occurs because of a bug in the version of the katello-change-hostname command in the 6.2 release. To avoid this problem, complete the upgrade to Satellite 6.3 before running the katello-change-hostname command.


Known Issue
Running the ./install_packages command when attempting to set up a disconnected Satellite Server fails and returns NOKEY error.
For more information, see the KCS Solution at


Known Issue
When using image-based provisioning against VMWare, attempting to add additional storage to the new host returns an error.


Known Issue

If you try to delete a subnet that is used to provision a machine, instead of receiving a user-friendly error message, you receive a confusing error message:

 | NoMethodError: undefined method `klass' for nil:NilClass
 | Did you mean?  class


Known Issue
If you have SELinux enabled, using Kerberos (KRB) keys instead of RSA keys can cause remote execution jobs to fail.


For ISO-based disconnected Satellite users

Known Issue
The RPM script is missing "--local", which makes it search the internet to install the "oauth" gem. For disconnected Satellites, this is a problem.

If Puppet 4 is installed, when yum installs packages using the default Puppet 4 repositories, before you run satellite-installer, enter the following command:

/opt/puppetlabs/puppet/bin/gem install --local /usr/share/foreman-installer/gems/oauth-0.5.1.gem


If you upgrade to Puppet 4, before you enter the --upgrade-puppet command, enter the following commands:

# yum remove -y puppet-server
# yum install puppetserver puppet-agent puppet-agent-oauth
/opt/puppetlabs/puppet/bin/gem install --local /usr/share/foreman-installer/gems/oauth-0.5.1.gem


Known Issue
Running katello-backup with a relative path for the destination, for example `katello-backup .', causes an error.
Run katello-backup with a full path. For example 'katello-backup /backup-destination'.