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. 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.

Starting with Satellite 6.4, two discovery rules in the same organization cannot have the same priority number. This was causing unexpected results previously. After the upgrade, discovery rules are prioritized according to the discovery framework.
Starting from Satellite 6.4, new postcreate and postupdate hook events are added to Satellite. In previous versions of Satellite, some host and hostgroup parameters were not passed to the hook object file by the create and update hook events. If you want all the host parameters fields in the hook object file, rename hooks directories from create to postcreate and from update to postupdate. No changes are required in the hook scripts.

Puppet Enterprise is not supported on Satellite Server. If you have it installed, perform the following actions to avoid conflicts after the upgrade:

  1. Move the cache from /var/lib/puppet/foreman_cache_data to /opt/puppetlabs/puppet/cache/:

    # mkdir -p /opt/puppetlabs/puppet/cache/
    # cp -r /var/lib/puppet/foreman_cache_data /opt/puppetlabs/puppet/cache/
  2. Run the satellite-installer --upgrade script to apply changes.
Starting from Satellite 6.4, the cron job to delete old reports is reconfigured to delete reports in batches of 1000 records with a fractional delay between tasks. This reduces the likelihood of updating workers becoming blocked. After the upgrade, monitor the number of reports in the database and the output of the report expiration tasks. In case of concurrency problems, update the check-in time for both the Puppet client, which is 30 minutes by default, and RHSM, which is four hours by default. This decreases the load on Satellite Server.
Satellite 6.4 introduces tighter restrictions around resource filter limitations. In previous versions of Satellite, the search query applied incorrect permissions to resources, which allowed users to perform tasks that were not permitted. This is now fixed.

In previous versions of Satellite, Satellite was able to retrieve templates from Capsules via the TFTP feature. Users were asked to enable TFTP and Templates modules on Capsules to have templating ability.

Starting from Satellite 6.4, Satellite uses the Templates feature to retrieve templates from Capsules. During the upgrade, Satellite will automatically set the Templates feature for all Capsules that also have the TFTP feature.

After the upgrade, verify that Templates feature is enabled for all Capsules that are supposed to have it. If not, navigate to Infrastructure > Capsules and click Refresh Features for all required Capsules. Then manually associate these Capsules with required subnets.


Starting from Satellite 6.4, the paths to the foreman discovery image are changed to conform with upstream:

  • boot/fdi-image-rhel_7-vmlinuz > boot/fdi-image/vmlinuz0
  • initrd=boot/fdi-image-rhel_7-img > boot/fdi-image/initrd0.img

    It was leading to issues with PXE templates previously. Now the new global templates already contains the new paths.

Telemetry in Satellite 6.4 will be functional after the pcp package version 4.1 or above is added to Red Hat Enterprise Linux Server 7. That is expected with the Red Hat Enterprise Linux 7.6 release.
In previous versions of Satellite, provisioning a host with VLAN interfaces on top of a bond interface resulted in an incorrect bond module configuration. It is now fixed with Satellite 6.4.

5.2. Deprecated Functionality

Docker plug-in

With this release, the Foreman Docker plug-in is deprecated and will be removed as part of a future release. This affects the container functionality that you can find in the Containers section of Satellite web UI.

Hammer Docker Command

With this release, the hammer docker command is deprecated and will be removed in Satellite 6.5.

Satellite Kickstart Default

With this release, the Satellite Kickstart Default provisioning templates are deprecated. All hosts consuming the now deprecated templates will be migrated automatically. Custom templates that are based on Satellite Kickstart Default are not considered during the migration, and need to be migrated manually.

Table 5.1. Deprecated Kickstart Default Templates

TemplatesReplacement Template

Satellite Kickstart Default

Kickstart Default

Satellite Kickstart Default User Data

Kickstart Default User Data

Satellite Kickstart Default Finish

Kickstart Default Finish

Satellite Atomic Kickstart Default

Atomic Kickstart Default

Satellite idm_register




Katello Service, Backup and Restore Commands

With this release, the following commands are deprecated. Ensure that you update your scripts appropriately.

Table 5.2. Deprecated Katello Commands

OptionsReplacement Options


foreman-maintain service


foreman-maintain backup


foreman-maintain restore

Installer Options

With this release, the following installer options are deprecated and removed in Satellite 6.4:

Table 5.3. Deprecated Installer Options



Superseded by


Hardcoded value for dynflowd.


Deprecated and replaced by certificates for authentication.


Deprecated parameter for configuring a yum repository from copr for EL6.


Deprecated parameter for older environment compatibility.


Replaced by foreman options.


Renamed to --katello-candlepin-oauth-{key,secret}.


Not used.


Deprecated with introduction of Puppet 5.

5.3. Known Issues

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


Known Issue

The change in navigation caused the Red Hat Access menu to no longer display. This issue will be fixed in an upcoming release.