Topic

Updated Satellite 6.4 packages that fix several bugs are now available for Red Hat Satellite.

Description

Red Hat Satellite is a system management solution that allows organizations to configure and maintain their systems without the necessity to provide public Internet access to their servers or other client systems. It performs provisioning and configuration management of predefined standard operating environments.

This update fixes the following bugs:

• After completing a sync, if only the product ID of the Content View changed, this update was not published in the Content View. (BZ#1664127)
• A manifest refresh was failing with the error "Failed to import archive". (BZ#1684691)
• virt-who was failing when pushing the information to Satellite Server. (BZ#1684693)
• Users now have increased control over Capsule sync policy and other traffic from Satellite to Capsule. (BZ#1684695)
• When 3 SLES were added to a custom product and then synced, an error occurred. (BZ#1684697)
• Capsule sync planning in foreman-tasks was taking too long. (BZ#1684698)
• There was a problem preventing a manifest refresh or expired pools job from completing. (BZ#1684700)
• The Capsule 05-pulp-https.conf file was using an old ProxyPass directive for GPG keys. (BZ#1684701)
• The manifest upload task was taking too much time. (BZ#1684703)
• The "yum remove java-1.7.0-openjdk" command was pulling in katello and Satellite as dependencies. (BZ#1684705)
• There was an error when uploading a manifest file on the disconnected Satellite Server. (BZ#1684706)
• The regenerate applicability tasks were failing because of a missing repository. (BZ#1684707)
• The default RSS feed has been updated to point to the new blog location. (BZ#1684708)
• There were sporadic timeouts when opening TCP connections that were preventing Satellite from upgrading. (BZ#1688317)
• When singleton actions from Dynflow's on_init playbook were run, they might not have started after an unclean shutdown. (BZ#1692806)

Users of Red Hat Satellite are advised to upgrade to these updated packages, which fix these bugs.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

For detailed instructions how to apply this update, refer to:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/upgrading_and_updating_red_hat_satellite/updating_satellite_server_capsule_server_and_content_hosts

Affected Products

• Red Hat Satellite 6.4 x86_64
• Red Hat Satellite Capsule 6.4 x86_64

Fixes

• BZ - 1664127 - productid is not published in the content view if that is the only item which changed in the sync
• BZ - 1684691 - Manifest refresh fails with error "Failed to import archive"
• BZ - 1684693 - virt-who is failing when pushing the information to the Satellite Server
• BZ - 1684695 - [RFE] User control of Capsule sync policy and other traffic from Satellite to capsule
• BZ - 1684697 - Unable to sync 3 SLES Update repositories
• BZ - 1684698 - Capsule sync planning in foreman-tasks sometimes takes too long
• BZ - 1684700 - Unable to refresh manifest or complete Expired Pools job
• BZ - 1684701 - Capsule 05-pulp-https.conf is using old ProxyPass directive for GPG keys (i.e missing the /v2/)
• BZ - 1684703 - Manifest upload task takes too much time
• BZ - 1684705 - `yum remove java-1.7.0-openjdk` pulls in katello and satellite as dependencies
• BZ - 1684706 - Error when uploading a manifest file on the disconnected Satellite Server
• BZ - 1684707 - Regenerate applicability fails when there is a missing repo
• BZ - 1684708 - Update default RSS feed to point to new Blog location
• BZ - 1688317 - sporadic timeouts in opening TCP connection prevents Satellite upgrades
• BZ - 1692806 - Singleton actions may not start after unclean shutdown

CVEs

(none)

References

(none)