vRA migration from 6.2.5 to 7.3 - All provisioning Advanced Service Blueprints and Actions are broken

[bdamian]

I have experienced an issue after migration from vRA 6.2.5 to 7.3, all Custom Resources and related Advanced Service Blueprints and Actions are broken. And when you try to fix it, you make more problems.

Suppose the following scenario:

In order to let your users do some stuff with their AD Users, you provision an AD:User as a custom object in vRA and create some related actions.

So, you create:

. Custom Resource: AD:User

. An Advanced Service Blueprint: Create User Object. This workflow takes the "requestedBy" and returns the corresponding AD:User. This object now appears in the "Items" tab.

. 4 Advanced Service Actions: with some actions for your custom resource (for example: change password)

(when you create and ADS Blueprint or Action, a Catalog Item or Action is created as well)

After you migrate from vRA 6.2.5 to 7.3, despite you can see the Custom Resource and Blueprints in XaaS Blueprints tab, nothing works. If you use Cloud Client, none of this content appears using "vra content list".

If you edit and save the AD:User custom resource (without touching anything) the object is updated and now appears in Cloud Client vra content list.

The same happens with ADS Blueprint and Actions but, instead to update the Catalog Items and Actions, new ones are created with the same names. All new AD:Users provisioned are related to the new Catalog Items and Actions, but all the Users provisioned before the upgrade, remain orphaned (no related actions are shown).

Now, in my actual scenario I have 5 Custom Resources with (almost) 4 Actions each, across multiple tenants.

Is there any workaround, fix, procedure I can do to prevent this before the upgrade (of fix after)?

Thanks a lot.

D.

[daphnissov]

This is one of the reasons I never upgrade customer from 6.x to 7.x. It's still highly problematic and breaks things. I know that doesn't exactly help you at this phase, but due to all the complexities of such a large leap you made, I'd open an SR and pull logs. This can get very complex to try and fix.

[bdamian]

What do you do instead of an upgrade from 6.x to 7.x, a migration? Is there any recommended way to do that for a large implementation with multiple tenants?

D.

[daphnissov]

If you already have a large environment with lots of managed resources and tenants then a new deployment of vRA 7 may not work for you. When I said "migration" I essentially meant a "new installation" and to set it up similar to what was in vRA 6. But, as I said, if you've already done the upgrade and it has broken a bunch of things, you'll have to work through those with VMware support as it can be a very complicated process.