Red Hat Ansible Automation Platform Release Notes

Red Hat Ansible Automation Platform 2.1

New features, enhancements, and bug fix information

Red Hat Customer Content Services

Abstract

A summary of new features, enhancements, and bug fix information for Red Hat Ansible Automation Platform.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Overview

Red Hat Ansible Automation Platform simplifies the development and operation of automation workloads for managing enterprise application infrastructure lifecycles. It works across multiple IT domains including operations, networking, security, and development, as well as across diverse hybrid environments. Simple to adopt, use, and understand, Red Hat Ansible Automation Platform provides the tools needed to rapidly implement enterprise-wide automation, no matter where you are in your automation journey.

1.1. What’s included in Ansible Automation Platform

Ansible Automation PlatformAutomation controllerAutomation hubAutomation services catalogInsights for Ansible Automation Platform

2.1.1

4.1.1

4.4.1

hosted service

hosted service

1.2. Red Hat Ansible Automation Platform life cycle

Red Hat publishes a product life cycle page that identifies the levels of maintenance for each Ansible Automation Platform release. See Red Hat Ansible Automation Platform Life Cycle for additional information.

1.3. Upgrading Ansible Automation platform

Use installer to perform upgrades to maintenance versions of Ansible Automation Platform. The installer performs all necessary actions required to upgrade to the latest versions of Ansible Automation Platform, including Ansible Tower and Private Automation Hub.

Important

Do not use yum update to run upgrades. Use installer instead.

Additional resources

Chapter 2. Red Hat Ansible Automation Platform 2.1

This release includes a number of enhancements, additions, and fixes that have been implemented in the Red Hat Ansible Automation Platform.

2.1. Ansible Automation Platform 2.1

Red Hat Ansible Automation Platform simplifies the development and operation of automation workloads for managing enterprise application infrastructure lifecycles. It works across multiple IT domains including operations, networking, security, and development, as well as across diverse hybrid environments. Simple to adopt, use, and understand, Red Hat Ansible Automation Platform provides the tools needed to rapidly implement enterprise-wide automation, no matter where you are in your automation journey.

2.1.1. Enhancements

  • Automation Mesh introduces separate execution capacity and update your cluster without downtime with Automation Mesh that connects the cluster with a flexible communication method using receptor
  • The platform installer can deploy a Highly Available (HA) Automation Hub cluster
  • Automation Hub connects instances to external Red Hat SSO instances and for the installer to deploy Red Hat SSO
  • Bundle installer provides the execution environment as part of the bundle
  • In the platform installer, rsync is not required anymore
  • The platform installer supports both with rsync and without rsync environment
  • Added support for sshpass 1.09
  • The platform operator has been upgraded to operator-sdk 1.11
  • Added support for OpenShift Container Platform 4.10
  • Added support for disconnected environment in the platform operator
  • Added support for SSO configuration for Hub in the platform operator
  • Added a must-gather container to help troubleshoot operator issues in the platform operator
  • Upgraded execution environment to ansible-core 2.12
  • Updated execution environment collections to core-2.12 compatible collections

2.2. Ansible Automation Platform 2.1.1

Enhancements

  • Added OCP 4.10 compatibility
  • Added support for HTTP proxy when pushing execution environment images
  • Added ability to configure nginx headers on Controller
  • Changed the setup.log file to no longer be world readable

Bug fixes

  • Fixed an issue during controller deployment where the web-container will fail to start up, resulting in a failed installation
  • Fixed a Server Error 500 that occurs after an Operator upgrade on OCP
  • Updated ansible-hub-ui to use a changelog

2.3. Ansible Automation Platform 2.1.2

Enhancements

  • Added architecture support labels for the Ansible Automation Platform operator
  • Updated to Receptor 1.2.1 on all supported versions of the Ansible Automation Platform
  • Removed unnecessary packages from the bundle installer to reduce the file size
  • Updated to version to Ansible Runner 2.1.3
  • Removed the enforcement of license compliance from the Ansible Automation Platform installer
  • Added support to enable an array of pull secrets to pass to the operator
  • Added a preflight check to ensure that the installer is running on a UTF-8 system
  • Removed unnecessary become_user:root entries from the Ansible Automation Platform installer
  • Added support to provide a custom secret key when running the rekey.yml file
  • Added a preflight check to detect missing username and password variables for service catalog worker, instead of causing an installation failure at a later point of time
  • Updated the collection counts on the Content tab when the collection details were filtered
  • Added guidelines for setting ORPHAN_PROTECTION_TIME

Bug fixes

  • Fixed an issue where Controller user interface would not load on a few cloud providers
  • Added compatibility with earlier versions for image_pull_secret key in awx-operator, so that the backup and restore operations are completed successfully
  • Automation controller backups no longer fail when multiple secrets are supported
  • Resolved certification mismatch during upgrade so that every controller dashboard is accessible
  • Improved the labels for Japanese translations
  • Resolved issues when upgrading automation hub from version 2.1.1 to version 2.1.2
  • Resolved issues where the Controller user interface was not accessible, when automation controller was installed through Operator on OpenShift Core Platform 4.10
  • Fixed an issue that caused the upgrade from Ansible Automation Platform 1.2 to 2.1 to fail, when the execution environment was transferred to automation hub
  • Fixed an issue so that a standalone installation of private automation hub can now transfer the execution environments to the hub
  • Resolved intermittent 500 internal server error while pushing the execution environments to automation hub that prevents images from being pushed to the hub
  • Fixed an issue when the variable sslmode was not configured correctly during automation hub installation
  • Running the `./setup.sh -b command from the installer directory no longer fails to load group variables
  • Fixed an issue where the SELinux context was not being configured correctly on subsequent installations
  • The installer no longer fails when IPV6 is disabled
  • Modified the database backup and restore logic to compress the data dump
  • Fixed an issue during installation where a configured proxy would not be used when required
  • Fixed installations of execution environments when installing without internet access
  • Creating default execution environments no longer fails when the password includes special characters
  • Added support to set a parameter to change the temporary directory path, so that the execution environments can be extracted to the bundled installer
  • Upgrading to Ansible Automation Platform 2.1 no longer fails when the Django superuser is missing
  • Fixed an issue where installation of automation hub failed due to symlinks
  • Added explanations for variables of service catalog worker in the installer inventory
  • Fixed an issue where installing automation hub with an external database did not install Postgres as expected
  • Fixed an issue where variables with default values were shown as undefined variables
  • Added support for ansible_host in the installer inventory for automation hub
  • Fixed an issue where a few commands were missing on initializing the container
  • Fixed an issue where the TTL controller caused the jobs to run repeatedly
  • Resolved intermittent 500 internal server error while pulling and pushing the execution environments from private automation hub
  • Fixed an issue so that remotes configured with proxy authentication can be edited without re-entering the proxy password
  • Updated the proxy password from text type to password type to make the password more secure
  • Updated the synchronization that is used by authenticated proxy to avoid authentication failures
  • Added message in the Controller user interface to inform users that the community collections do not have docs
  • Added field validation to allow HTTPS URLs only when adding a remote registry
  • Added import result and filenames to the audit log
  • Updated the group categories such as Namespaces, Collections, Users, Groups, Remotes, and Containers in the translatable strings
  • Updated the Filter by repository dropdown field in the translatable strings
  • Updated the Namespaces label in the translatable strings
  • Fixed an issue where artifacts were removed from the entire repository when reclaim space was triggered with image removal

2.4. Ansible Automation Platform 2.1.3

Enhancements

  • Updated the version to Openshift-clients 4.10.x
  • Updated the version to pulpcore-selinux 1.3.2
  • Updated the version to pulp_installer 3.15.9-3
  • Updated the version to Receptor 1.2.3
  • Added an enhancement such that execution environment images can now be pulled from automation controller only
  • Modified the base images of execution environments so that the controller backups are executed in the container

Bug fixes

  • Task container no longer fails for Controller Operator 2.1.3
  • The setup log now gets updated when it is run as non-root on bastion host
  • The users' time zones are now populated correctly in the execution environments
  • Installation of automation hub no longer causes SELinux errors
  • Syncing the execution environments from registry.redhat.io on automation hub 2.1 no longer causes [Too many open files] errors
  • Enhanced the copy process of execution environments so that they require less space in the `/tmp directory
  • The receptor no longer fails in FIPS mode
  • Added the no_proxy definition in the inventory file so that deployments no longer use proxy when accessing private automation hub and thereby run successfully
  • The bundled installer no longer fails while finding registry details
  • Bundle installation no longer fails with skopeo file permissions error
  • Installation of Red Hat Single Sign On (SSO) on private automation hub no longer fails
  • Bundle installation of private automation hub no longer pushes images with missing ee_image_base that leads to installation failure
  • When you run the `./setup.sh -b command during an upgrade, the API tokens are now maintained
  • The super user role of users can now be changed by administrators only
  • Improved the tasks for collections deletion so that the collections are now deleted from both the repositories and the disks
  • While using automation hub 4.5.0 with central authentication, the hub user interface no longer turns unresponsive when the group permissions are modified
  • Added localization support for Modules, Roles, Plugins, and Dependencies counter in container list for both card and list view
  • Updated the documentation link to route to documentation of the correct version
  • Resolved intermittent issue while trying to sync community devsec.hardening collection on automation hub 4.4.0
  • Improved import log and status overflow pages in automation controller UI
  • Added visibility for execution environments created by ansible-builder in the automation hub UI
  • Resolved an issue while copying and removing content from a repository by changing lock and transaction into a single task
  • Updated orphan cleanup task to improve collection re-upload experience
  • Resolved an issue where a list of execution environments available and discovered were not displayed after indexing
  • Updated user access to be able to customize minimum password length

2.5. Ansible Automation Platform 2.1.4

Enhancements

  • Rebuilt the bundle installer to pick up the latest python-pulp-container rpm and container images.
  • Updated RSA key strength for Ansible Automation Platform certificates.

Bug fixes

  • A password is now asked for when running ad-hoc commands and selecting the credential.
  • Fixed an error during installation where the skopeo directory was created.
  • Fixed an error caused by ansible-core version conflicts during the upgrade from 1.2 to 2.1.
  • Fixed an issue where survey fields couldn’t be updated on the web console if they were created using the API.
  • Fixed an issue where the date picker would select dates in the past, and this would prevent saving.
  • Fixed an issue where setting Use Role in credential resulted in unwanted roles being added to other users.
  • Fixed an issue where execution environments were failing to be pushed locally during install.
  • Fixed an issue where facts gathered while using slices were not stored in Ansible Automation Platform.
  • Fixed an issue where filter options were being removed when navigating between job template pages.
  • Fixed an issue where the launched job was vanishing from the Jobs page.
  • Fixed an issue where the installer failed at "Push execution environment images locally on Automation Controller and Execution Nodes" and was unable to make rootless runtime.
  • Fixed an issue where idle connections were growing and not closing in the automation hub database.
  • Fixed an issue where private automation hub was unable to restore with an external database.
  • Fixed an issue where hub installed unnecessary extra packages.

2.6. Automation Hub

Automation Hub allows you to discover and utilize new certified automation content from Red Hat Ansible and Certified Partners. On Ansible Automation Hub, you can discover and manage Ansible Collections which is supported automation content developed by both partners and Red Hat for use cases such as cloud automation, network automation, security automation, and more.

Automation Hub 4.4.1 enhancements and bug fixes

  • Added tasking system permissions so that users with the appropriate permissions can view and manage tasks
  • Added name, namespace name, and registry requirements when add/editing an execution environment
  • Fixed an error where certified collections will fail to install from a private hub
  • Fixed a bug where the registry sync status will not display on the remote registries page

Automation Hub 4.4.3 Bug fixes

  • Fixed an issue where idle connections were growing and not closing in the automation hub database.
  • Fixed an issue where private automation hub was unable to restore with an external database.
  • Fixed an issue where hub installs unnecessary extra packages.

2.7. Automation controller

Automation controller replaces Ansible Tower. Automation controller introduces a distributed, modular architecture with a decoupled control and execution plane. The name change reflects these enhancements and the overall position within the Ansible Automation Platform suite.

Automation controller provides a standardized way to define, operate and delegate automation across the enterprise. It also introduces new, exciting technologies and an enhanced architecture that enables automation teams to scale and deliver automation rapidly to meet ever-growing business demand.

Automation controller 4.1 new features and enhancements

  • Separate control and execution layers.
  • Automation execution environments are container images that provide a standardized way to build and distribute environments where automation runs.
  • Automation mesh allows distributed execution across on-premises environments, the hybrid cloud, and the edge. It replaces Ansible Tower and isolated nodes.

Automation controller 4.1 deprecated and removed features

  • Support for custom Python virtual environments for execution.

See Automation controller Release Notes for 4.x for a full list of new features and enhancements.

Automation controller 4.1.1 Enhancements and Bug fixes

  • Added the ability to specify additional nginx headers
  • Fixed analytics gathering to collect all the data the controller needed to collect
  • Fixed the controller to no longer break subsequent installer runs when deleting the demo organization

See automation controller Release Notes for 4.x for a full list of new features and enhancements.

Automation Controller 4.1.4 Bug fixes

  • Fixed an issue where the installer failed at "Push execution environment images locally on Automation Controller and Execution Nodes" and was unable to make rootless runtime.

Legal Notice

Copyright © 2023 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.