Unable to publish blueprint in VCF Automation. Error "Cannot create new version: Error: VRO action #### not found"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When migrating from VMware Aria Automation to VCF Automation, users may experience failures when attempting to publish a draft blueprint to a released version. While the Deploy or Test functions work correctly, publishing fails with the following error:

Cannot create new version: Error: VRO action #### not found

Environment

VCF Automation 9.0.x

Cause

In VCF Automation 9.x, format validation has been added to the "publish" task.

E.g. If a blueprint input format is "date-time", the vRO action must also return a "date" format.

Aria Automation 8.18.x did not have the same format validation.

Resolution

This issue is under review with Broadcom Engineering.

Subscribe to this knowledge article to get updates on this issue.

Additional Information

Workaround: To prevent the validation error, ensure the Orchestrator action returns the same type/format as the input.

E.g. If a blueprint input format is "date-time" [In UI: Type: String, More Options -> Format: "Date Time"], the Orchestrator action must also return a "date" format.

Example Input:

Example Orchestrator Action: