If you encounter issues when configuring or using a VMware Cloud Director cloud account in vRealize Automation you can consult logs and other resources as described below.

Troubleshooting VMware Cloud Director cloud account connection issues

If the VMware Cloud Director adapter is not listed on the cloud account creation screen or is not responding, you can use the following command to verify the status by logging in to the vRealize Automation kubernetes host and checking the adapter pod status: 

root@host [ ~ ]# kubectl -n prelude get pods | grep adapter-host-service-app
adapter-host-service-app-65f5c945bb-p6hpn      1/1     Running   0          4d1h

If the VMware Cloud Director adapter cannot communicate with the Cloud Director physical machine, an error is displayed in the cloud account screen with statements about connection and processing exceptions. The error also appears in the logs.

Working with VMware Cloud Director logs

The VMware Cloud Director adapter main log file resides under the local (pod) dir /var/log/adapter-host-service-app.log and in the case of the adapter running inside the vRealize Automation appliance host, this log is also copied to /services-logs/prelude/adapter-host-service-app/file-logs/. By default most of the logging is restricted to DEBUG or INFO levels. You can alter the configuration for the following loggers to enable more verbose logging for debugging purposes:
  • org.apache.cxf.services=INFO - this logger provides verbose info for communication between the adapter and VMware Cloud Director.
  • com.vmware.vra.vcloud.director.adapter=TRACE - this logger provides verbose info for communication between the adapter and vRealize Automation.
There are three ways you can access the logs:

  • access log by login to the adapter pod

    root@host [ ~ ]# kubectl -n prelude exec -ti adapter-host-service-app-65f5c945bb-p6hpn -- bash
root [ / ]# less /var/log/adapter-host-service-app.log
  • access log using kubectl
    root@host [ ~ ]# kubectl -n prelude get logs adapter-host-service-app-65f5c945bb-p6hpn
  • access log using the adapter kubernetes host local copy
    root@host [ ~ ]#  less /services-logs/prelude/adapter-host-service-app/file-logs/adapter-host-service-app.log
You can query or change the loggers configuration via /actuator/loggers REST API endpoint.
  • Example of enabling VMware Cloud Director client communication tracing via curl :
    curl -i -X POST -H 'Content-Type: application/json' -d '{"configuredLevel": "INFO"}'
 http://{adapter-url}/actuator/loggers/org.apache.cxf.services
  • Example of disabling VMware Cloud Director client communication tracing via curl : 
    curl -i -X POST -H 'Content-Type: application/json' -d '{"configuredLevel": "OFF"}'
 http://{adapter-url}/actuator/loggers/org.apache.cxf.services
  • Example of obtaining current configuration for VMware Cloud Director client communication via curl :
    curl http://{adapter-url}/actuator/loggers/org.apache.cxf.services
...
{"configuredLevel":"OFF","effectiveLevel":"INFO"}

There are other parameters that can be adjusted to alter performance of VMware Cloud Director.

  • vcd.max.thread.count - this parameter determines the maximum degree of parallelism when performing VMware Cloud Director API calls. The default is 128.
    Note: Decreasing the value for this parameter will reduce the stress on the VMware Cloud Director backend when performing enumeration but may decrease the enumeration performance.
  • VCD_ADAPTER_PAGINATION_SIZE_IMAGES - this parameter determines the page size when performing image enumeration. The default is 50.
    Note: Decrease this parameter if adapter timeout errors occur during image enumeration.