Stage#.#####: Failed to resolve endpoints. Reason: 400 BAD_REQUEST "One or more endpoints not found."
book
Article ID: 406292
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
In Pipelines within Aria Automation, create a new Pipeline.
Add an Aria Orchestrator Workflow as 1 stage.
At the 2nd stage add some additional parameters.
You notice that this pipeline runs correctly from Pipelines but when we publish this to a catalog then we proceed to hit the error:
Failed to resolve endpoints. Reason: 400 BAD_REQUEST "One or more endpoints not found."
Environment
Aria Automation 8.18.1 Patch 1, Patch 2 & Patch 3
Cause
Customer's pipeline which was created originally in 1 project which is likely shared with another project.
From the Catalog service, the pipeline was triggered from a different project, the "Pipelines" project, which is treated separately.
.
The "Pipelines" project's model is referring to a vRO endpoint in the task where parameters are set.
This endpoint was created again in the same project and cannot be accessed from outside this pipeline.
When the created pipeline is triggered from Catalog ( a different project from "Pipelines"), its not able to find the endpoint and is resulting in expected error with 400 status.
Directly executing this from the "Pipelines" page works since execution is triggered from "Pipelines" project itself and hence all of the endpoints & variables referred to are accessible.
Resolution
Recreate all the referred to Endpoints and variables in the "Catalog" project.
I.e.: Add the Endpoints and variables as configurable variables to the catalog item