Release Notes

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.

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.

Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.

Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.

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.

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.

With this release, the virt-who agent can now be installed on the same machine where the main Satellite Server is hosted.

With this release, the virt-who agent can now be installed on the same machine where the main Satellite Server is hosted.

With this release, the default root password hash has been made SHA256 instead of MD5. This improves the default security of all provisioned hosts.

With this release, the default root password hash has been made SHA256 instead of MD5. This improves the default security of all provisioned hosts.

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.

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.

With this release, a "Test Connection" button was added to verify LDAP connection information.

With this release, a "Test Connection" button was added to verify LDAP connection information.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

With this release, the backup script has been updated to perform incremental backups of the raw packages. This speeds up all subsequent backups.

With this release, the backup script has been updated to perform incremental backups of the raw packages. This speeds up all subsequent backups.

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.

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.

As part of upgrading to the latest Puppet 3.x version, the hiera package has now been updated to 1.3.

As part of upgrading to the latest Puppet 3.x version, the hiera package has now been updated to 1.3.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The gutterball engine has been removed from Red Hat Satellite 6.2. The data stored in gutterball was never used.

The gutterball engine has been removed from Red Hat Satellite 6.2. The data stored in gutterball was never used.

Elastic Search has been removed from Red Hat Satellite. It has been replaced by the standard searching provided by the database.

Elastic Search has been removed from Red Hat Satellite. It has been replaced by the standard searching provided by the database.

The Hammer Import tool is marked for deprecation and cannot be used in future versions of Satellite. For transitioning hosts after this release, use the bootstrap script. For more information see, https://access.redhat.com/articles/2280691

The Hammer Import tool is marked for deprecation and cannot be used in future versions of Satellite. For transitioning hosts after this release, use the bootstrap script. For more information see, https://access.redhat.com/articles/2280691