VMware Cloud Community
prateek_sahoo
Contributor
Contributor

vROps management pack upgrade from 6.3 to 6.7 fails during installation

Hi,

We have developed a pack v1.0 with 6.3 vROps SDK. Currently we have upgraded the pack v2.0 with 6.7 vROps SDK.

Changes in v2.0 pack:

1. SDK change from 6.3 to 6.7

2. Folder structure change as per 6.7 (content folder introduced)

During installation of both the packs, we found below things

1. Fresh installation for both the packs works fine.

2. Upgrade(overriding pack) from v1.0 to v2.0 fails during installation. It fails after pre-script.

How can we resolve this upgrade failure issue?

Reply
0 Kudos
9 Replies
RobertMesropyan
VMware Employee
VMware Employee

Hello

Do  you see any error in view-bridge.log file(s)?

Reply
0 Kudos
prateek_sahoo
Contributor
Contributor

Hi RobertMesropyan,

Found the root cause. The world object name has been changed. Because of which the pack upgrade failed.

Still not able to find the correct solution. Do you know how to resolve this?

Reply
0 Kudos
RobertMesropyan
VMware Employee
VMware Employee

Hello!

Please advise how the world object name was changed. Approved way is update it by using "worldObjectName" attribute in describe.xml

Reply
0 Kudos
prateek_sahoo
Contributor
Contributor

In pack 1.0 the world object name key was "worldObjectName" in describe.xml. Which was changed to "world Object Name" in the next version of the pack in describe.xml file. So while upgrading the pack from 1.0 to 2.0 (with overriding the content check box enabled), pack is not getting upgraded.

As there can only be on world object, vROps pack installation fails.

Reply
0 Kudos
RobertMesropyan
VMware Employee
VMware Employee

You should not change key, instead of it you can customize just object name.

Please refer to this sample (key="Storage World"  is constant😞

from

 <ResourceKind key="Storage World" nameKey="40" showTag="true" type="8" subType="6" worldObjectName="Storage World object">

ti

 <ResourceKind key="Storage World" nameKey="40" showTag="true" type="8" subType="6" worldObjectName="New Storage World object">

Reply
0 Kudos
prateek_sahoo
Contributor
Contributor

Is there any way to change the key of the world object?

The scenario is, world object key has been changed in our product and we are facing upgrade issue.

Is there any work around or some scripts which we can include in the prescript?

Reply
0 Kudos
RobertMesropyan
VMware Employee
VMware Employee

Probably, you see in view-bridge.log something like "ERROR [DistTaskSolutionManagerDistributedTask] com.vmware.vcops.bridge.plugin.server.SolutionManagerDistributedTask.installSolution - Could not process describe for adapter "RMAdapter": RuntimeException: java.lang.RuntimeException: Describe would remove resources, so we are failing describe. Problem resource kind is " ?

By design object type cannot be removed from describe.xml if any object exists, what's why I am recommending to keep old key and just update a name.

If you still want to change a key I can suggest the to delete old world object from pre-script by using REST API (delete resource) or ask customer to delete it from UI before upgrade

Reply
0 Kudos
prateek_sahoo
Contributor
Contributor

Deleting the resource will result into loss of data. Is there any way to change the key without any data loss?

Reply
0 Kudos
RobertMesropyan
VMware Employee
VMware Employee

Changing the key means to change object type, so i'ts impossible to prevent data loss
Reply
0 Kudos