Upgrade to vRO 7.3 from 6.x breaks Dynamic Types

[bdamian]

I've noticed that vRO 7.3 came with Dynamic Types version 1.3 and it breaks all configurations from the version 1.0.x.

After the upgrade, all configurations are broken, all vRA Custom Resources, related XaaS Blueprints and related XaaS Actions are broken. Trying to fix all this is a very complicated and if you have a large deployment with several tenants its even worse.

Is there any way to upgrade in a way that all keep working?

D.

[iiliev]

Hmm, plug-in upgrade from 6.x to 7.3 is expected to work automatically.

Are the problems you are experiencing after upgrade specific to functionality on vRA/XAAS side? Could you check if the upgraded dynamic type stuff works on vRO side? Also, could you compare the resource element containing dynamic type configuration (under Library > DynamicTypes > Configuration) to check what exactly is changed/removed after the upgrade?

[bdamian]

Hi Ilian,

After the upgrade, nothing works.

Even the Resource Folder is different. In previous version it was /Resources/Library/Dynamic Types (with a space between the words), and now is /Resources/Library/DynamicTypes (without space). In the previous version, the configuration file was a json and now is a XML with a json in it.

The configuration was no migrated, so nothing works.

D.

[iiliev]

I think these 2 changes (no space in the category name and format change) should not cause problems, as the new plug-in version should handle them.

Not sure if it will work, but one thing you can try is to export the configuration as package before upgrade (using the workflow 'Export Configuration As Package' under Library > DynamicTypes > Configuration), then export the package file using vRO client, then do the 6.x-to-7.x upgrade, delete the DT broken configuration (the resource element), restart vRO server (to get rid of runtime information for broken DT), and then import the configuration again, using the workflow 'Import Configuration From Package' (note: importing the old configuration by simply importing the package file won't work).

[bdamian]

I've already done that, but the problem is that in vRA, all Custom Resources are broken. If I edit and save each Resource, its like if a new Resource is created instead. Then, XaaS blueprints and Action dont work.

I could even repairer them, but the new problem is that all previous object I've deployed, doesn't work any more.

It is terrible and I dont know what to do.

D.

[pjw]

Hi Damian, we experienced a similar issue and have an open SR with VMware.

If you are using an external vRO server for your dynamic types, try logging in as the vRA system administrator (administrator@vsphere.local) and changing the default tenant vRO configuration to use your external server. Despite setting the vRO configuration as the Tenant Admin we found the dynamic types plugin was using the default tenants vRO configuration which was left as embedded following the 6.2 migration.

[bdamian · Accepted solution]

After some more tests, I've noticed that even Dynamic Types lose his configurations, you can configure it again if you export the configuration as a Package earlier. So, the recommendation is, export Dynamic Types as a package before you upgrade vRO 6.x to 7.3.

But there is a new problem with the upgrade from vRA 6.2.5 to vRA 7.3 and is that all Custom Resources became broken. But this if for a new thread in other forum.

D.