"Error processing CSV file: project doesn't exist with the name" while running a workflow in Aria Orchestrator

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Aria Orchestrator workflow fails to locate/Process projects beyond the first 500. 

• This results in the error "Error processing CSV file: project doesn't exist with the name - Project_name" for projects exceeding this limit.

Environment

• VMware Aria Automation 8.x

• VMware Aria Orchestrator 8.x

Cause

• The Aria Automation IAAS API (Get /iaas/api/projects) used by the Orchestrator workflow has a default pagination limit of 500 projects. 

• This limit restricts the workflow's ability to access and recognize projects beyond this number.

• The API call Get /iaas/api/projects is used to fetch project names.

• The API response may show the following information if there are more than 500 projects:

  • "totalElements" as 612

  • "numberOfElements" as 500

• This indicates that the API call has a hard-coded limit of 500 projects, so the Orchestrator considers and will only list the first 500 projects.

• Any workflow which utilizes this API, exceeding this limit fails with the error: "Error processing CSV file: project doesn't exist with the name - Project_name" as the complete list of Projects wouldn't be listed.

Resolution

To Overcome this issue, please follow the below steps:

• Modify the API call to include the $top parameter to fetch all projects.

• The API call Get /iaas/api/projects should be modified as follows in the workflow:

  • https://Aria_Automation_FQDNorIP/iaas/api/projects?$top=612

• This ensures that all 612 projects are retrieved, overriding the default limit of 500.

• Modify the workflow to incorporate the $top parameter to retrieve all projects dynamically.

• Implement pagination to handle larger project datasets efficiently.

Additional Information

• The Aria Automation UI can access all projects, indicating the limit is specific to the API call within the Orchestrator workflow.

• The IAAS API's "totalElements" and "numberOfElements" fields confirm the default pagination limit.

• Refer to the Broadcom documentation on Using Pagination and Count for detailed information on handling pagination in Aria Automation APIs.