VMware Cloud Community
bdamian
Expert
Expert

NSX-v DynamicTypes plug-in V2 and Orchestrator 6.0.1 install problem

Hi all,

I'm trying to install the "com.vmware.coe.plugin.dynamictypes.nsx.v2.package" in a newly installed vRealize Orchestrator 6.0.1 virtual appliance. I've just deployed the appliance and this was my first task afterwards.

I've followed the specified steps here NSX-v Dynamic Types plug-in V2

  • I've download and rename the package
  • I've imported the package
  • I've runned the "Plugin gen -1- Install plug-in" workflow.

This workflow throw the following error:

[2015-04-06 11:42:42.212] [W] InternalError: Unable to remove resource element, reason : org.springframework.transaction.TransactionSystemException: Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Transaction marked as rollbackOnly

And then, the workflow stucks on "importNamespaceResourceElementToConfiguration" Action.

Attached is a screen shot of my Orchestrator console running the "Plugin gen -1- Install plug-in" workflow.

Thanks a lot,

D.

---
Damián Bacalov
vExpert 2017-2023 (7 years)
https://www.linkedin.com/in/damianbacalov/
https://tecnologiaimasd.blogspot.com/
twitter @bdamian
Reply
0 Kudos
6 Replies
cdecanini_
VMware Employee
VMware Employee

Does it happen if you delete a resource element manually ?

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
bdamian
Expert
Expert

Sorry but I don't understand your question. What resource?

I've just import the package and run the workflow.

Any ideas?

D.

---
Damián Bacalov
vExpert 2017-2023 (7 years)
https://www.linkedin.com/in/damianbacalov/
https://tecnologiaimasd.blogspot.com/
twitter @bdamian
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

The workflow fails when trying to delete resource element programmatically.

To check if this is a specific 6.0.1 issue you can try to delete a resource element in the vCO client

Also it is possible this error happens with a particular DB type and not another.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

In any case I would recommend opening an SR. There may be workarounds.

In the meantime you can comment the part deleting the resource element. Deleting these allows to not have to overwrite these when you do another import (newer version of the plug-in or another plug-in).

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos
bdamian
Expert
Expert

Is this an official plugin and I can send a support request?

Despite the error and the delay, it seems to work now. I don't know the reason, is a newly installed vRO without any plugin added.

Thanks.

D.

---
Damián Bacalov
vExpert 2017-2023 (7 years)
https://www.linkedin.com/in/damianbacalov/
https://tecnologiaimasd.blogspot.com/
twitter @bdamian
Reply
0 Kudos
cdecanini_
VMware Employee
VMware Employee

It is not but deleting a resource element via the scripting is a supported vRO feature.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
Reply
0 Kudos