Unable to save or version ABX actions in VMware Aria Automation when a Bitbucket integration is enabled

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Unable to save or version ABX actions in VMware Aria Automation when a Bitbucket integration is enabled. While creating new actions works, attempting to save a version of an existing action results in a generic "Something went wrong" message in the UI and an "Error on attempt to commit version" in the browser developer console. 

Environment

VMware Aria Automation 8.18.1

Cause

The issue is caused by the Bitbucket server's requirement for a valid email address to be associated with the authenticated user performing a Git commit. If the service account used for the Aria Automation integration does not have the mail attribute populated in Active Directory, Bitbucket rejects the commit with an `ArgumentValidationException` in the cgs-service logs. The Aria Automation `cgs-service` logs will show: `External API error [400] ... message: When performing an edit, the authenticated user must have an e-mail address.` 

Resolution

To resolve this issue, ensure that the account configured for the Bitbucket integration has a valid email address:

1. Locate the service account used for the Bitbucket integration in your Active Directory. Ensure the mail attribute is populated with a valid email address. 
2. Log into Bitbucket using the service account and verify that an email address is displayed in the user profile settings.
3. In Aria Automation, navigate to Infrastructure > Connections > Integrations, select the Bitbucket integration, and click Validate followed by Save to ensure the updated account metadata is recognized. 
4. Attempt to save a version of an ABX action. The commit should now succeed without error.