Ansible Automation Platform/Ansible Tower no longer working in Aria Automation after upgrading to AAP 2.5 and later (including AAP 2.7)

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After upgrading AAP (Ansible Automation Platform) to version 2.5 or later (including AAP 2.7), AAP integration is no longer working in Aria Automation 8.x and VCF Automation 9.x. In newer versions such as AAP 2.7, API calls may fail due to endpoints like /api/controller being unexpectedly truncated or removed after the call.

 

Environment

Aria Automation 8.x.

VCF Automation 9.x

Cause

This has been identified as a product limitation resulting from architectural changes introduced by RedHat.

• Starting in AAP 2.5, RedHat introduced a Platform Gateway which deprecated and removed the /api/v2/ base path

• As per AAP documentation, API endpoints /api/v2/* have shifted towards /api/controller/v2/*.

• Aria Automation's current integration architecture relies on the older API structure and is incompatible with the new AAP API changes.

Resolution

Supporting these newer versions of AAP requires significant new roadmap development rather than a standard break/fix patch, this has been officially classified as a Product Enhancement / Feature Request.

To restore functionality, customers must use an earlier (supported) version of AAP/Tower (AAP 2.4 or older).

Please review the VMware Aria Automation Support Matrix for a complete list of tested and supported AAP versions.