Chapter 5. Release Information

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

BZ#1329051

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.

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 https://access.redhat.com/support/offerings/techpreview/.

BZ#1376191

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.

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#1432285

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.

BZ#1433458

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

BZ#1435007

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.

BZ#1469599

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(',')}

BZ#1552093

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.

BZ#1512959

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.

BZ#1560607

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.

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 bootstrap.py. For more information, see Importing Existing Hosts via the Bootstrap Script.

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

BZ#1321041

BZ#1382090

BZ#1445625

BZ#1507848

BZ#1518848

BZ#1523392

BZ#1538597

BZ#1541002

BZ#1541481

BZ#1541885

For ISO-based disconnected Satellite users

BZ#1544401