In multi-tenant vRO, when trying to export the Dynamic types, the "Export Configuration As Package" workflow fails.
book
Article ID: 330782
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
To address the issues with vRA upgrade. While upgrading to vRA 7.6 stuck on Export Configuration with a failure to create package.
Symptoms:
In multi-tenant vRO, when trying to export the Dynamic types, the "Export Configuration As Package" workflow fails. Some of the finder workflows or actions have been created in a tenant different than the system tenant.
Cause
vRO plugins are not tenant-aware. All content regarding the plugins (configurations, finder workflows, etc. ) should be in the system tenant.
Resolution
Move the content to the system tenant.
Take a snapshot of the system
Log in into one of the user tenants
Create a package and manually add to it all actions and workflows related to the dynamic types you wish to export. After you save the package, if your actions and workflows have referenced other items, they should be there as well.
Export the package and save it.
Delete the actions you added to the package and after that delete the action categories. Repeat the same with all other items in the package if there are any.
Log into the other user tenants (if there are such) and also delete the same actions and categories from there.
Log in as administrator in the system tenant and import the package from step 4.
You should be able then to export the dynamic types.
If you are doing a migration, ensure that you are importing the dynamic types as administrator in the system tenant.