"No converter available" error vCloud Director plugin inventory fails to load in Aria Orchestrator

Products

• VMware Aria Suite

Issue/Introduction

• Errors similar to the following are visible in the /var/log/services-log/prelude/vco-app/file-logs/vco-server-app.log logfile:
  
  

2024-04-11T09:13:19.590Z ERROR vco [host='vco-app-<AppID>' thread='http-nio-8280-exec-2' user='' org='-' trace='-'] {} com.vmware.vmo.plugin.vcloud.VCloudPluginFactory - com.thoughtworks.xstream.converters.ConversionException: No converter available
---- Debugging information ----
message : No converter available
type : javax.xml.namespace.QName
converter : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
message[1] : Unable to make field private static final long javax.xml.namespace.QName.serialVersionUID accessible: module java.xml does not "opens javax.xml.namespace" to unnamed module @6538c5d5
-------------------------------
        at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:88)
        at com.thoughtworks.xstream.XStream$1.lookupConverterForType(XStream.java:478)

• Folders including the admin organization and vDCS folders fail to load / enumerate when browsing the Orchestrator clients Inventory view.
• Workflows vCloud:Organization.GetVdcs() or VDC.getVApps may fail with the above errors

Environment

VMware Aria Automation Orchestrator 8.x

VMware Aria Automation Orchestrator 8.14.x, 8.16.x, 8.17.0

Cause

The issue may occur due to the VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director plugin's incompatibility with the orchestrator version in use.

On versions 8.14-8.17 where Java 17 is used, the issue is seen in some cases on updated plugin versions. 

Resolution

First, attempt to resolve the issue by installing VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.5.1.1 or higher.

Note: before upgrading the plugin validate that the version is compatible with your version of Orchestrator by referencing the Product Interoperability Matrix.

 

Workaround

If the functions aren't returning on updated plugin versions, the following reconfiguration of the Orchestrator pod may help:

1. Check if the vRO pod profile exists:
   ls -l /etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco/90-resources.yaml
2. If the above outputs No such file or directory then create the containing directory:
   mkdir /etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco
3. Next, edit this profile file, for example:
   vim /etc/vmware-prelude/profiles/custom-profile/helm/prelude_vco/90-resources.yaml
4. If there is already some configuration here, for example heap memory specification, leave it here. Add these lines:
   

   serverEnv: {
     "JVM_OPTS": "$(JVM_OPTS) --add-opens=java.xml/com.sun.org.apache.xerces.internal.jaxp.datatype=ALL-UNNAMED --add-opens=java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED"
   }

5. Repeat these steps 1-4 for other nodes, if using clustered Orchestrator
6. Restart the cluster:
   /opt/scripts/deploy.sh