Red Hat Ansible Automation Platform Release Notes

Red Hat Ansible Automation Platform 2.4

New features, enhancements, and bug fix information

Red Hat Customer Content Services

Abstract

This guide provides 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.

Providing feedback on Red Hat documentation

We appreciate your feedback on our technical content and encourage you to tell us what you think. If you’d like to add comments, provide insights, correct a typo, or even ask a question, you can do so directly in the documentation.

Note

You must have a Red Hat account and be logged in to the customer portal.

To submit documentation feedback from the customer portal, do the following:

  1. Select the Multi-page HTML format.
  2. Click the Feedback button at the top-right of the document.
  3. Highlight the section of text where you want to provide feedback.
  4. Click the Add Feedback dialog next to your highlighted text.
  5. Enter your feedback in the text box on the right of the page and then click Submit.

We automatically create a tracking issue each time you submit feedback. Open the link that is displayed after you click Submit and start watching the issue or add more comments.

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 hubEvent-Driven Ansible controllerInsights for Ansible Automation Platform

2.4

4.4

  • 4.7
  • hosted service

1.0

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. Refer to Red Hat Ansible Automation Platform Life Cycle.

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

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

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. New features and enhancements

This release of Ansible Automation Platform features the following enhancements:

  • Previously, the Execution Environment container images were based on RHEL 8 only. With Ansible Automation Platform 2.4 onwards, the Execution Environment container images are now also available on RHEL 9. The Execution Environment includes the following container images:

    • ansible-python-base
    • ansible-python-toolkit
    • ansible-builder
    • ee-minimal
    • ee-supported

  • The ansible-builder project recently released Ansible Builder version 3, a much-improved and simplified approach to creating execution environments. You can use the following configuration YAML keys with Ansible Builder version 3:

    • additional_build_files
    • additional_build_steps
    • build_arg_defaults
    • dependencies
    • images
    • options
    • version

For more information about using Ansible Builder version 3, see Ansible Builder Documentation and Execution Environment Setup Reference.

  • Ansible Automation Platform 2.4 and later versions can now be run on ARM platforms, including both the control plane and the execution environments.
  • Added an option to configure SSO logout URL for automation hub.
  • Updated the ansible-lint RPM package to version 6.14.3.
  • Updated django for potential denial-of-service vulnerability in file uploads (CVE-2023-24580).
  • Updated sqlparse for ReDOS vulnerability (CVE-2023-30608).
  • Updated django for potential denial-of-service in Accept-Language headers (CVE-2023-23969).

2.1.2. Deprecated and removed features

Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in Ansible Automation Platform and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.

The following is a list of major functionality deprecated and removed within Ansible Automation Platform 2.4:

  • On-premise component Automation Services Catalog is now removed from Ansible Automation Platform 2.4 onwards.
  • With the Ansible Automation Platform 2.4 release, the Execution Environment container image for Ansible 2.9 (ee-29-rhel-8) is no longer loaded into the Automation Controller configuration by default.
  • Although you can still synchronize content, the use of synclists is deprecated and will be removed in a later release. Instead, private automation hub administrators can upload manually-created requirements files from the rh-certified remote.
  • You can now configure the Controller Access Token for each resource with the connection_secret parameter, rather than the old tower_auth_secret parameter. This change is backwards compatible, but the tower_auth_secret parameter is now deprecated and will be removed in a future release.
  • Smart inventories have been deprecated in favor of constructed inventories and will be removed in a future release.

2.1.3. Bug fixes

The following bugs were fixed in this release of Ansible Automation Platform:

  • Installer now ensures that collection auto signing cannot be enabled without enabling the collection signing service.
  • Fixed an issue with restoring backups when the installed automation controller version is different from the backup version.
  • Fixed an issue with not adding user defined galaxy-importer settings to galaxy-importer.cfg file.
  • Added missing X-Forwarded-For header information to nginx logs.
  • Removed unnecessary receptor peer name validation when IP address is used as the name.
  • Updated the outdated base_packages.txt file that is included in the bundle installer.
  • Fixed an issue where upgrading the Ansible Automation Platform did not update the nginx package by default.
  • Fixed an issue where an awx user was created without creating an awx group on execution nodes.
  • Fixed the assignment of package version variable to work with flat file inventories.
  • Added a FQDN check for the automation hub hostname required to run the Skopeo commands.
  • Fixed an issue such that the front end URL for Red Hat Single Sign On (SSO) is now properly configured after you specify the sso_redirect_host variable.
  • Fixed the variable precedence for all component nginx_tls_files_remote variables.
  • Fixed the setup.sh script to escalate privileges if necessary for installing Ansible Automation Platform.
  • Fixed an issue when restoring a backup to an automation hub with a different hostname.

2.1.4. Technology Preview

Some features in this release are currently classified as Technology Preview. Technology Preview features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. Please note that Red Hat does not recommend using technology preview features for production, and Red Hat SLAs do not support technology preview functions.

Following are the technology preview features:

  • Ansible Automation Platform 2.4 adds the ability to install the automation controller for IBM Power (ppc64le), IBM Z (s390x), and IBM® LinuxONE (s390x) architectures.

Additional resources

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

Enhancement

  • This release of automation hub provides repository management functionality. With repository management, you can create, edit, delete, and move content between repositories.

Bug fixes

  • Fixed an issue in the collection keyword search which was returning an incorrect number of results.
  • Added the ability to set OPT_REFERRALS option for LDAP, so that users can now successfully log in to the automation hub using their LDAP credentials.
  • Fixed an error on the UI when redhat.openshift collection’s core dependency was throwing a 404 Not Found error.
  • Fixed an error such that the deprecated execution environments are now skipped while syncing with registry.redhat.io.

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

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

2.4. Event-Driven Ansible

Event-Driven Ansible is the newest capability of Ansible Automation Platform that is designed to enable automated response with user-defined, rules-based workflows. Event-Driven Ansible works by receiving events from third party tools, deciding on the actions to take, and acting automatically.

Event-Driven Ansible is included in Ansible Automation Platform, making the platform even more capable as a single enterprise automation solution. Using Event-Driven Ansible, domain experts can easily create end-to-end fully automated OpsAsCode scenarios for a broad array of use cases across the IT landscape. By eliminating high-volume routine tasks and automatically responding to changing conditions, teams are free to innovate more efficiently, and act consistently and accurately at scale.

Known issues

  • Certain characters, such as hyphen (-), forward slash (/), and period (.), are not supported in the event keys.
  • Both contributor and editor roles cannot set the AWX token. The AWX token can be set by users with administrator roles only.
  • Activation-job pods do not have request limits.
  • The onboarding wizard does not request a controller token creation.
  • Users cannot filter through a list of tokens under the Controller Token tab.
  • Only the users with administrator rights can set or modify their passwords.
  • In the event of a failure, an activation with restart policy set to Always is unable to restart the failed activation.
  • Disabling and enabling an activation causes the restart count to increase by one count. This behavior results in an incorrect restart count.
  • When all workers are busy with activation processes, other asynchronous tasks are not executed, such as importing projects.
  • Podman pods must be executed with memory limits.
  • Long running activations with loads of events can cause out of disk space issue.
  • Users can add multiple tokens even when only the first AWX token is used.
  • A race condition occurs when creating and rapidly deleting an activation causes multiple errors.
  • When users filter any list, only the items that are on the list get filtered.
  • When ongoing activations start multiple jobs, a few jobs are not recorded in the audit logs.
  • When a job template fails, a few key attributes are missing in the event payload.
  • Restart policy in a Kubernetes deployment does not restart successful activations that are marked as failed.
  • An incorrect status is reported for activations that are disabled or enabled.
  • If the run_job_template action fails, the rule is not counted as executed.
  • RHEL 9.2 activations cannot connect to the host.
  • When there are more activations than available workers, disabling the activations incorrectly shows them in running state.
  • Event-Driven Ansible activation pods are running out of memory on RHEL 9.
  • Restarting the Event-Driven Ansible server can cause activation states to become stale.
  • Bulk deletion of rulebook activation lists is not consistent, and the deletion can be either successful or unsuccessful.
  • When users access the detail screen of a rule audit, the related rulebook activation link is broken.

2.5. Automation Platform Operator

Ansible Automation Platform Operator provides cloud-native, push-button deployment of new Ansible Automation Platform instances in your OpenShift environment.

Enhancements

  • Starting with Ansible Automation Platform 2.4, the Platform Resource Operator can be used to create the following resources in automation controller by applying YAML to your Openshift cluster:

    • Inventories
    • Projects
    • Instance Groups
    • Credentials
    • Schedules
    • Workflow Job Templates
    • Launch Workflows

One notable change is that you can now configure the Controller Access Token for each resource with the connection_secret parameter, rather than the old tower_auth_secret parameter. This change is backwards compatible, but the tower_auth_secret parameter is now deprecated and will be removed in a future release.

Bug fixes

  • Enabled configuration of resource requirements for automation controller init containers.
  • Added securityContext for EDA Operator deployments to be Pod Security Admission compliant.
  • Resolved error Controller: Error 413 Entity too large when doing bulk updates.
  • Ansible token is now obfuscated in YAML job details.

2.6. Ansible Automation Platform Documentation

The documentation set for Red Hat Ansible Automation Platform 2.4 has had significant updates to improve the experience for our customers and the Ansible community.

Enhancements

  • With the removal of the on-premise component Automation Services Catalog from Ansible Automation Platform 2.4 onwards, all Automation Services Catalog documentation is removed from the Ansible Automation Platform 2.4 documentation.

  • The following documents are created to help you install and use Event-Driven Ansible, the newest capability of Ansible Automation Platform:

In addition, sections of the Ansible Automation Platform Planning Guide and the Ansible Automation Platform Installation Guide are updated to include instructions for planning and installing Event-Driven Ansible.

  • The name of the Managing Red Hat Certified and Ansible Galaxy collections in automation hub Guide has changed to include validated content and is now Managing Red Hat Certified, validated, and Ansible Galaxy content in automation hub.
  • The Ansible Automation Platform 2.4 Release Notes are restructured to improve the experience for our customers and the Ansible Community. Users can now view the latest updates based on the Ansible Automation Platform versions, instead of their release timeline.
  • The document Managing repositories in automation hub is created to help you create and manage custom repositories in automation hub.

Chapter 3. Red Hat Ansible Automation Platform 2.3

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

3.1. Ansible Automation Platform

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.

Enhancements

  • Fixed a race condition where the UI would not properly populate upon launch.
  • Fixed an issue where puppet managed files are not handled properly by the set-up script.
  • Fixed an issue where self-signed certs were being recreated on every run of setup.sh.
  • Added an option for execution environment images to be pulled from Hub only.
  • Fixed an issue where the bundled installer was failing when DNF was trying to fetch gpg keys remotely.
  • Upgraded pulp_installer to 3.20.5+ .
  • Implemented sidecar documentation to allow easy documentation of filter and test plugins, as well as documentation for non-python modules without requiring a .py file for documentation.
  • Migrated display for stdout and stderr from the display class to proxy over the queue for dispatch in the main process to improve reliability of displaying information to the terminal.
  • Moved handler processing into the configured strategy, so that handlers operate within the configured strategy, instead of using a non-configurable linear like execution of handlers.
  • Updated internal FieldAttribute classes to act as Python data descriptors to reduce code complexity and use of metaclasses.
  • Fixed an issue when ansible-runner was not properly removed from hybrid nodes when upgrading to Ansible Automation Platform 2.2.

Technology preview features

Some features in this release are currently classified as Technology Preview. Technology Preview features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. Please note that Red Hat does not recommend using technology preview features for production, and Red Hat SLAs do not support technology preview functions.

The following are the technology preview features:

  • Added the ability to use external execution nodes when running AAP as a managed service in Azure.
  • Added the ability to use external execution nodes when running the AAP Operator in Openshift.

Other noteworthy developer tooling updates include the following:

  • Added new pre-flight checks to ansible-core CLI start up to enforce assumptions made about handling display and text encoding.
  • Added official support for Python 3.11 to ansible-core CLIs and target node execution.
  • Dropped Python 3.8 support for ansible-core CLIs and controller side code.
  • Added lint profile support for content pipelines.

Additional resources

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

Enhancements

  • Adopted the new pulp RBAC system.
  • Added a configurable automatic logout time. Set a minimum password length for internal users.
  • Added the capability to configure LDAP with private automation hub.
  • Added visibility for execution environments created by ansible-builder in the automation hub UI.
  • Fixed an error when navigating to a non-existent group URL.
  • Fixed an issue where roles could not be created through the UI.
  • Fixed an issue with Hub installation during the collect static content task.
  • Fixed an issue when a 500 error would populate when listing roles on a group.
  • Fixed an issue when imports contained more than 100 namespaces.
  • Fixed an issue where filters were not working correctly when searching for execution environments.
  • Fixed an issue where certified content would display incorrectly in private automation hub when synced.
  • Fixed an issue where group_admin users could not view groups.
  • Fixed an issue where pressing the enter key would reload a form instead of submitting.
  • Fixed an issue with broken links on community collection dependencies.
  • Fixed an issue with roles not showing up on a group access page.
  • Fixed some issues with how roles were displayed on the groups page.
  • Updated so that only admins can change the superuser status on users.
  • Updated so that the screen no longer hangs when attempting to edit a group with unknown permissions.
  • Updated the installer to use a custom repo that automation hub will add to show validated content.
  • Updated the pulp_ansible package to 0.15.x.
  • Updated the pulp_container package to 2.14.
  • Upgraded pulpcore to 3.21.x.
  • Fixed problem in which the released date for collections in private automation hub was the same as the released date for that collection and its versions in the console.redhat.com automation hub.
  • Deprecated the pulp_firewalld_zone parameter, replacing it with the automationhub_firewalld_zone parameter.

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

Enhancements

  • Fixed the Ansible Galaxy Credential to no longer be automatically created or added to organizations after removing it manually.
  • Fixed an issue where warnings were being unnecessarily displayed.
  • Included updates and enhancements to task manager for scaling jobs, mesh, and cluster size to improve performance.
  • Included reaper and periodic task improvements for scaling the mesh and jobs, which improve performance.
  • Fixed an issue with webhook notifications not triggering for some job template runs.
  • Fixed a race condition where the UI would not properly populate upon launch.
  • Added UI support for filtering single select survey question answers when configuring a job.
  • Fixed an issue where execution environments were failing to be pushed locally during installation.
  • Fixed an issue where inventory could not be selected in workflows even if the user has admin permissions on the workflow.
  • Introduced a content signing utility through the Command Line Interface called ansible-sign that provides options for the user to sign and verify whether the project is signed.
  • Added project or playbook signature verification functionality to controller, enabling users to supply a GPG key and add a content signing credential to a project. This automatically enables content signing for said project.

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

3.4. Automation Platform Operator

Ansible Automation Platform Operator provides cloud-native, push-button deployment of new Ansible Automation Platform instances in your OpenShift environment.

Enhancements

  • Fixed an issue where the pulp resource manager was not removed on upgrade from Automation Platform Operator 2.1 to Automation Platform Operator 2.2.

3.5. Ansible Automation Platform Documentation

The documentation set for Red Hat Ansible Automation Platform 2.3 has been refactored to improve the experience for our customers and the Ansible community. These changes will make it easier for you to install, migrate, backup, recover and implement new features.

Enhancements

  • The Red Hat Ansible Automation Platform Installation Guide has been restructured into three separate documents to include the following:

    Red Hat Ansible Automation Platform Planning Guide
    Use this guide to understand requirements, options, and recommendations for installing Ansible Automation Platform.
    Red Hat Ansible Automation Platform Installation Guide
    Use this guide to learn how to install Ansible Automation Platform based on supported installation scenarios.
    Red Hat Ansible Automation Platform Operations Guide
    Use this guide for guidance on post installation activities for the Ansible Automation Platform.

  • The Red Hat Ansible Automation Platform Operator Installation Guide has been renamed to Deploying the Red Hat Ansible Automation Platform operator on OpenShift Container Platform. The document has also been updated to include the following:

    • Migration procedures so you can migrate your existing Ansible Automation Platform deployment to Ansible Automation Platform Operator.
    • Upgrade procedures so you can upgrade to the latest available version of the Ansible Automation Platform Operator.
  • The Red Hat Ansible Automation Platform Operator Backup and Recovery Guide has been added to the library to help you backup and recover installations of the Red Hat Ansible Automation Platform operator on OpenShift Container Platform.
  • The Ansible Builder Guide has been renamed to Creating and Consuming Execution Environments to better reflect the information provided in the guide.

Chapter 4. Red Hat Ansible Automation Platform 2.2

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

4.1. Ansible Automation Platform 2.2

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.

Enhancements

  • Added the Automation Services Catalog as an on-prem component for the Ansible Automation Platform. Automation Services Catalog is a Technology Preview supported feature in Ansible Automation Platform 2.2.
  • Added support for RHEL 9 for automation controller, private automation hub, and private services catalog.
  • Components of the Ansible Automation Platform now run with python 3.9 runtime.
  • Ansible Automation Platform now deploys with PostgreSQL 13, Nginx 1.20 and Redis 6.
  • The Ansible Automation Platform installer will now use certificates signed by a common certificate authority (CA) when certificates are not provided.
  • The Ansible Automation Platform installer is now provided as a package in the automation platform channels, allowing users to retrieve the installer without leaving their server using the dnf install command.
  • Added Korean localization in the UI for automation controller, automation hub, and services catalog.
  • Added ansible-core 2.13 to the ee-minimal and ee-supported containers.
  • Added collection signing and verification as Technology Preview supported features in Ansible Automation hub.
  • Ansible Builder now supports the verification of signatures in collection content when building execution environments (Technology Preview)

Other noteworthy developer tooling updates include the following:

  • ansible-lint is available as a technology preview. It is a command-line tool that further enhances the content creation experience by proven practices, patterns, and behaviors. See New features and changes for ansible-navigator for more information.
  • Automation content navigator v2.0 now includes more features to create content more easily. See New features and changes for ansible-lint for more information.
  • An updated VS Code extension provide language support for creating Ansible content, including smart auto-completion of related playbook content, syntax highlighting, jinja helpers, and direct integrations with supported tooling. See New features and enhancements for vscode-ansible for more information.

4.2. Ansible Automation Platform 2.2.1

Enhancements

  • Modified installer to include the ansible-builder image
  • Updated the openshift-clients to 4.10.x
  • Enabled users to use certificates located on destination nodes
  • Updated the version to pulpcore-selinux 1.3.2
  • Updated the version to pulp_installer 3.18
  • Enhanced the copy process of execution environments so that they require less space in the /tmp directory
  • Updated RSA key strength for Ansible Automation Platform certificates
  • Removed redhat.rhv collection from supported execution environments due to Python dependencies
  • Modified the base images of execution environments so that controller backups are executed in the container
  • Added the capability to configure LDAP with private automation hub

Bug fixes

  • Fixed an issue where package dependencies were missing on execution nodes
  • The setup log now gets updated when it is run as non-root on bastion host
  • The pulp resource manager now gets removed when the Ansible Automation Platform is upgraded from 2.1 to 2.2
  • The receptor.service now restarts as expected when you run the automation-controller-service commands
  • The installer no longer fails with permission errors in the `/home/pulp directory
  • The receptor no longer fails in FIPS mode
  • Installer no longer fails with error in installing the semanage dependency
  • Updated the default configuration of GALAXY_COLLECTION_SIGNING_SERVICE to ansible-default instead of TRUE
  • Installation no longer fails due to conflicting ansible-builder Python packages
  • Upgrade from Ansible Tower to Ansible Automation Platform 2.1 no longer fails due to non-root user error
  • Controller database no longer gets unpacked on all nodes and cause disk space issues
  • Installation of high availability automation hub no longer fails on a shared Netapp storage
  • Ansible Automation Platform 1.2 to 2.1 upgrade no longer fails with 502 error due to wrong SELinux content set on nginx
  • Installer no longer fails to generate SSO key pair for IPV6
  • The group permissions editor can now be used to set permissions for the group when external authorization is enabled
  • 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
  • The Deprecated label now appears immediately after an action click or after the page reload on automation hub UI
  • Upon clicking the Undeprecate button for a collection on automation hub UI, an alert is displayed stating that the task has started with a link of the task
  • After syncing the Red Hat certified collections and their versions in private automation hub, the UI now correctly displays the release date of the collection and not the synchronization date
  • Updated the default namespace logo to make it appear similar to the Ansible product logo
  • Automation hub UI now displays the selected collection similar to the rest of the selections
  • Reenabled the Deprecate button for collections in Insights mode on automation hub UI

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

Enhancements

  • Added functionality for collection signing and verification in Ansible Builder.
Note

Collection signing and verification are Technology Preview supported features.

4.4. Automation Services Catalog

Automation Services Catalog provides an easy way to extend automation in your Ansible controller to a broader user base. It offers multi-level approval to ensure extending automation is done safely. And, Role Based Access allows you to restrict automation access to specified users. Automation Services Catalog is the shop window into the Ansible Automation Platform.

Note

Automation Services Catalog is a Technology Preview supported feature.

The following languages are supported for internalization:

  • English
  • French
  • Spanish
  • Japanese
  • Korean
  • Dutch
  • Chinese

Enhancements

  • Private Automation Services Catalog can now be installed. Installation must be on a physical/virtual instance.
  • Red Hat Single Sign-On can now be installed. Installation must be on a separate physical/virtual instance.
  • Added role-based access for users and groups.
  • Added ability to order products that contain job templates or workflows within portfolios.
  • Extended metadata to describe products.
  • Added functionality for an admin to share Portfolios to users.
  • Added functionality to copy products and portfolios.
  • Added option for multi-level approval process before a product can be executed.
  • Added the approver role, who can approve, deny, or memo approval requests in a queue.
  • Added ability to email approval requests.
  • Added re-branding functionality to allow customers to change the default product icons and logos to match their organization.

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

Enhancements

  • Introduced the mesh visualizer feature that generates a visual representation of your mesh topology
  • Automation controller now automatically mounts the system trust store in execution environments during job runs for VM-based installs
  • Added log format for 4XX errors to allow customization of 4xx error messages that are produced when the API encounters an issue with a request
  • Added ability to use labels in inventory files
  • Added ability to flag users as superusers and auditors in SAML integration
  • Automation controller now uses Python 3.9

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

4.6. Automation Platform Operator

The Ansible Automation Platform Operator provides cloud-native, push-button deployment of new Ansible Automation Platform instances in your OpenShift environment.

Deprecated functionality

  • The image_pull_secret (string) variable has been deprecated and will no longer be supported in a future release. You should now use the image_pull_secrets (array) variable on the spec when creating an Automation Hub or Automation Controller custom resource. This new variable allows you to specify multiple pull secrets as an array, for example: 
spec:
  image_pull_secrets:
    - redhat-operators-pull-secret
    - my-other-pull-secret

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

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

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

5.2. Ansible Automation Platform 2.1.1

Enhancements and bug fixes

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

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

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
  • 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 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
  • Resolved intermittent issue while trying to sync community devsec.hardening collection on automation hub 4.4.0
  • 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.

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

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

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

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

5.7.1. Automation controller

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.

5.7.2. Automation controller

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.

Chapter 6. Red Hat Ansible Automation Platform 1.2

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

6.1. Ansible Automation Platform 1.2.1 Installer

Ansible Automation Platform can be installed in various ways by choosing the best mode for your environment and making any necessary modifications to the inventory file. See Installing Ansible Automation Platform for more information.

Platform Installer bug fixes and enhancements

  • Updated the installer to ensure Automation Hub repositories are only enabled while running the installer
  • Updated the installer to allow it to pin a specific version of Automation Hub that needs to be installed
  • Fixed the installer to only install the DB where it belongs and not on all nodes
  • Fixed the installer to only check the RHSM Automation Hub repository when not using a bundled installer

6.2. Red Hat Ansible Automation Platform 1.2.4

Bug fixes

  • Added the ability for Ansible Automation Platform 1.2.x to transition from venvs to execution environments smoothly to platform 2.x This includes three new awx-manage commands, check associations, and export venvs for building an execution environment.
  • Added Ansible 2.9.25 to the platform installer package
  • Fixed Tower’s NGINX Instance vulnerability (CVE-2021-23017). For any deployments on RHEL 8, the package comes from RHEL, and just applying the RHEL update resolves this.
  • Updated the backup and restore to now work without the automationhub group

6.3. Ansible Automation Platform 1.2.6

Enhancements and bug fixes

  • Updated openshift-clients package that ships with Ansible Tower 3.7 and 3.8
  • Modified database backup and restore logic to compress dump data
  • Added ability to provide custom secret key when running rekey.yml
  • Fixed a bug where the selinux-policy was not recognized during installation

6.4. Ansible Tower 3.8.0

Ansible Tower helps teams centralize and control your IT infrastructure with a visual dashboard, role-based access control, job scheduling, integrated notifications and graphical inventory management. Easily embed Ansible Automation into existing tools and processes with REST API and CLI.

New Features

  • Subscription activation can now be done via connecting to Red Hat Satellite, or by importing a subscription manifest.
  • You can now integrate directly with Private Automation Hub as a source of content for Ansible Automation, and configure the priority of your content sources.
  • Inventory sources are now configured via full YAML inventory plugin configuration, allowing access to the full set of available customization and grouping options.

See Ansible Tower Release Notes v3.8.0 for a full list of new features and enhancements.

6.4.1. Ansible Tower 3.8.1

Bux fixes and enhancements

  • Improved analytics collection to collect the playbook status for all hosts in a playbook run
  • Updated nginx on RHEL 7
  • Updated autobahn
  • Added aggregation support for applying multiple subscriptions to a single Tower installation
  • Fixed Tower to properly handle certain uploaded subscription manifests
  • Fixed Tower to properly respect the configured destination port when interacting with Red Hat Satellite 6 to obtain licensing/entitlement data
  • Fixed an error in the module documentation for the tower_license module* Fixed inventory updates from Satellite 6 and Tower to no longer fail unexpectedly
  • Fixed AWS inventory hosts to now properly track across inventory updates

See Ansible Tower Release Notes v3.8.1 for a full list of new features and enhancements.

6.4.2. Ansible Tower 3.8.2

Bux fixes and enhancements

  • Upgraded to the latest oVirt inventory plugin to resolve a number of inventory syncing issues that can occur on RHEL7
  • Upgraded to the latest theforeman.foreman inventory plugin to resolve a few bugs and performance regressions
  • Upgraded to a more recent version of Django to address CVE-2021-3281
  • Upgraded to a more recent version of autobahn to address CVE-2020-35678
  • Fixed a security issue that allowed a malicious playbook author to elevate to the awx user from outside the isolated environment https:https://access.redhat.com/security/cve/cve-2021-2025[CVE-2021-20253]
  • Fixed several issues related to how Tower rotates its log files
  • Fixed the installer to no longer prevent Tower from installing on RHEL8 with certain non-en_US.UTF-8 locales
  • Fixed unanticipated delays in certain playbook output
  • Fixed job runs to no longer fail for playbooks that print certain types of raw binary data
  • Fixed the generation of unnecessary records in the Activity Stream when Ansible Automation data is collected
  • Fixed PostgreSQL backups to no longer fail when a non-default PostgreSQL username is specified
  • Fixed access to encrypted Tower settings to prevent intermittent failures that caused failed job launches
  • Fixed unexpected failures on certain long-running jobs running on isolated nodes
  • Deprecated the global /api/v2/job_events/ endpoint, which will be removed in a future release

See Ansible Tower Release Notes v3.8.2 for a full list of new features and enhancements.

6.4.3. Ansible Tower 3.8.3

Bux fixes

  • Analytics collection no longer cause lost job events when Tower is under load
  • Analytics collection now handles null characters in job event output
  • Pending jobs in /api/v2/metrics show correct counts
  • Project updates are no longer delayed when projects contain large files
  • Status for hosts are properly counted in notification payloads
  • SAML organization creation now properly assigns a default Galaxy credential
  • SAML configuration now properly denotes required SAML contact fields
  • Fixed a race condition in settings updates that previously lead to incorrect behavior
  • Log messages are updated to be more clear when rsyslog is unresponsive

See Ansible Tower Release Notes v3.8.3 for a full list of new features and enhancements.

6.5. Ansible Tower 3.8.4

Bux fixes

  • Running inventories of ~60k hosts no longer takes a very long time for events to show up
  • Removed artifact_data from data sent to analytics as part of playbook_on_stats, since artifact_data can contain PII or sensitive data
  • Updated Django version to 2.2.20
  • Regular users are no longer experiencing longer load times than a superuser when clicking to edit a job template
  • Updated password validation support to allow modifying password complexity requirements using some Django configurations
  • Fixed AWS inventory tags filtering to support the OR condition
  • Fixed a python-urllib3 vulnerability (CVE-2021-33503)

See Ansible Tower Release Notes v3.8.4 for a full list of new features and enhancements.

6.5.1. Automation Hub 4.2.0

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.

Private Automation Hub

  • Use the new private Automation Hub, which is hosted on-premises or on the cloud of your choice, to synchronize and manage this automation for enterprise use. Administrators can synchronize any desired certified Content Collections from Ansible Automation Hub into private Automation Hub, in addition to their own content, to provide a curated library of content for reusing and sharing across your internal automation community.

6.5.2. Automation Hub 4.2.1

Private Automation Hub bug fixes and enhancements

  • Fixed NamespaceLink creation and Validation on duplicated name
  • Fixed a bug where API returns 409 in case of existing group with same name
  • Updated the namespaces api to perform a partial match on namespace name and namespace company name when using the 'keywords' query parameter
  • Fixed KeyError lookup in namespace and collection viewset
  • Fixed error in error msg when importing invalid filenames
  • Enhanced content sync to better deal with Akamai rate limits

6.5.3. Automation Hub 4.2.2

Automation Hub bug fixes and enhancements

  • Fixed the galaxy-importer check for max size of docs files
  • Removed ability for uses to delete themselves
  • Prevented users with delete-user permissions from deleting admin users
  • Obfuscated token and password on the API docs for /sync/config
  • Split the proxy_url into 3 fields: username, password, and address
  • Fixed ability to remove credentials from advanced options for repository sync
  • Added a new component to indicate when a secret field is set or not

6.5.4. Automation Hub 4.2.3

Automation Hub bug fixes

  • Fix how travis checks for existence of Jira issues
  • Fixed synclist curation creating 2 * N tasks, where N is number of synclists. Now synclist curation is executed in batches. Number of batches is configured in project settings. By default it is set to 200 synclists per task.
  • Fix NamespaceLink creation and Validation on duplicated name.
  • API returns 409 in case of existing group with same name.
  • The namespaces api now performs a partial match on namespace name and namespace company name when using the 'keywords' query parameter.
  • Fix KeyError lookup in namespace and collection viewset
  • Fix error in error msg when importing invalid filenames
  • Fix the galaxy-importer check for max size of docs files
  • Only show synclist toggles to org admin. Non-org admins should get 403 response when viewing synclist endpoints.
  • Users should not be able to delete themselves regardless of having 'delete-user' permissions.
  • Prevent users with delete-user perms from deleting admin users
  • Make token and password obfuscated on the API docs for /sync/config
  • split proxy_url in 3 fields: username, password, address
  • Fix groups endpoint viewable only by admin
  • Expose pulp API in generated openapi spec.
  • Replace current PULP_REDIS* env variables with PULP_REDIS_URL env variable to accommodate PULP_REDIS_SSL.

6.5.5. Automation Hub 4.2.4

Automation Hub bug fixes

  • Fix "CVE-2021-32052 django: header injection" by moving to django 2.2.23
  • Download collection artifacts from the galaxy apis instead of the pulp content app

6.5.6. Automation Hub 4.2.6

Automation Hub bug fixes

  • Implemented filters for state and keywords on imports API
  • Create 'inbound-namespaces' whenever a namespace is created

6.5.7. Automation Services Catalog

Automation Services Catalog provides lifecycle management, provisioning, retirement and cataloging of your automation resources. It works across multiple Ansible Automation Platform clusters allowing holistic analytics of automation across your entire infrastructure. It provides access to automation content in physical, virtual, cloud and container environments. Use this catalog when you need to control, organize, govern, and share automation content as well as when you must meet security and compliance requirements regarding the use of content.

Technology Preview

  • Connect your on-premise Ansible Tower infrastructure to communicate with Automation Services Catalog by installing the Receptor plug-in.

New Features

  • Use the new order process features to integrate Automation Services Catalog with an Information Technology Service Management (ITSM) systems such as ServiceNow.

Chapter 7. Red Hat Insights for Red Hat Ansible Automation Platform

Insights for Ansible Automation Platform gives you feedback about your automation deployments through insights and governance which allow you to view information about automation health, usage, and performance across your enterprise.

June 2021 release

This release introduces the automation savings planner to Insights for Ansible Automation Platform. The automation savings planner is a tool where users can track their automation efforts by creating automation savings plans, each with a defined set of tasks needed to complete their plans. Users can also view a calculation of their cost savings from automating these tasks.

  • Create an automation savings plan by specifying a list of tasks needed to complete an automation job.
  • Review the status of the various automation savings plans in your organization using the planner list view.
  • Link a job template to an associated automation savings plans.
  • Calculate the cost and monetary savings for an automation savings plan by reviewing the Statistics view in each plan.

October 2021 release

This release introduces reports to Insights for Ansible Automation Platform. The reports feature on the Ansible Automation Platform provides users with a visual overview of their automation efforts across different teams using Ansible. The reports feature that gives you a visual overview of how your Ansible automation environment is running, across a variety of metrics. Each report is designed to help users monitor the status of their automation environment, be it the frequency of playbook runs or the status of hosts affected by various job templates.

Chapter 8. Red Hat Automation Analytics October 2020 release

8.1. Introduction

Red Hat Automation Analytics give you analytics and real-time feedback about your automation deployments through insights and governance which allow you to view information about automation health, usage, and performance across your enterprise.

8.2. New Features

This Red Hat Automation Analytics release includes the following features:

  • The Job Explorer provides a detailed view of jobs run on Ansible Tower clusters across your organizations. You can access the Job Explorer by directly clicking on the navigation tab or using the drill-down view available across each of the application’s charts. See Evaluating your {ControllerName} jobs runs using the Job Explorer to learn more.

8.3. Enhancements

This Red Hat Automation Analytics release includes the following enhancements:

  • A date filter on the Automation Calculator;
  • Additional details added to top templates.

8.4. Bug fixes

This release of Red Hat Automation Analytics includes the following bug fix:

  • Scaling on the Automation Calculator is corrected.

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.