Red Hat Ansible Automation Platform Release Notes

Red Hat Ansible Automation Platform 1.2

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.

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 PlatformAnsible TowerAutomation HubAutomation Services CatalogInsights for Ansible Automation Platform

1.2.0

3.8.0

4.2.0

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

1.3. Upgrading Ansible Automation platform

Perform upgrades to maintenance versions of Ansible Automation Platform using the installer. 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.

Refer to the table in What’s included in Ansible Automation Platform for information on maintenance releases of Ansible Automation Platform.

See Ansible Automation Platform Quick Installation Guide for procedures on using the Ansible Automation Platform installer.

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

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

2.2. Red Hat Ansible Automation Platform 1.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.

Bux 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

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

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

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

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

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

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

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

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

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

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

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

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

2.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 3. 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 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 4. Red Hat Automation Analytics October 2020 release

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

4.2. New Features

October 2020

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 Ansible Tower jobs runs using the Job Explorer to learn more.

4.3. Enhancements

October 2020

This Red Hat Automation Analytics release includes the following enhancements:

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

4.4. Bug Fixes

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

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