The vRealize Automation adapter configuration in vRealize Operations by VMware Cloud Foundation is in an error state.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• The vRealize Automation Adapter instance Collection Status on the Administration-->Solutions page in vRealize Operations is Error.
• The vRealize Automation Solution Status on the Administration-->Solutions page is Collection Failed (1).
• You see messages similar to the following in the /storage/log/vcops/log/adapters/VCACAdapter/VCACAdapter_###.log file on the vRealize Operations Manager node where the vRA adapter instance resides:

2018-10-29 09:16:29,301 WARN [Collector worker thread 10] (178) com.vmware.adapter3.vcac.VCACAdapter.onCollect - Tenant vsphere.local has privilege issues. Hence skipping for another tenant. Error is : User account rights problem. Please ensure the super user has fabric administrator privileges for fabrics in the following tenant: vsphere.local
2018-10-29 09:21:26,113 ERROR [Collector worker thread 24] (178) com.vmware.adapter3.vcac.VCACAdapter.onCollect - For input string: ""
2018-10-29 09:21:26,114 ERROR [Collector worker thread 24] (178) com.vmware.adapter3.vcac.VCACAdapter.onCollect - Error encountered during collection: For input string: ""
java.lang.NumberFormatException: For input string: ""
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:592)
        at java.lang.Integer.parseInt(Integer.java:615)
        at com.vmware.adapter3.vcac.VCACAdapter.checkIfAdapterCollectionRequired(VCACAdapter.java:1229)
        at com.vmware.adapter3.vcac.VCACAdapter.onCollect(VCACAdapter.java:832)
        at com.integrien.alive.common.adapter3.AdapterBase.collectBase(AdapterBase.java:745)
        at com.integrien.alive.common.adapter3.AdapterBase.collect(AdapterBase.java:530)
        at com.integrien.alive.collector.CollectorWorkItem3.run(CollectorWorkItem3.java:46)
        at com.integrien.alive.common.util.ThreadPool$WorkerItem.run(ThreadPool.java:253)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Foundation 3.0.x

Resolution

This is a known issue affecting VMware Cloud Foundation 3.0.x. There is currently no resolution.

Workaround:
To workaround this issue, use the following steps to delete and recreate the vRealize Automation adapter instance in vRealize Operations.

1. Log in to vRealize Operations Manager as a user with administrative privileges.
2. Navigate to the Administration page and then select Solutions.
3. Select the VMware vRealize Automation solution and click the Configure button.
4. Select vRealize Automation Adapter - <vRA load balancer short name> (vsphere.local)
5. Make a note of all settings as they will be re-used when re-creating the adapter instance.
6. Click the Delete button. Ensure the Remove related objects checkbox is selected. Click the YES button. Click the CLOSE button.
7. Select the VMware vRealize Automation solution and click the Configure button. Complete the wizard with the following information (or the information that was noted in Step 5):

Display Name: vRealize Automation Adapter - <vRA load balancer name> (vsphere.local)
Description: vRealize Automation vsphere.local Tenant
vRealize Automation Appliance URL: https://<vRA load balancer FQDN>

8. Click the dropdown button next to Credential and select the configured vRA credential.
9. Click the Edit Credential button.
10. Change the SuperUser Username from [email protected] to the tenant admin account configured during vRA deployment.
11. Change the SuperUser Password value to the password for the previously configured tenant admin account.
12. Click the OK button.
13. Expand Advanced Settings.
14. Set Tenants to vsphere.local and leave all other settings at the default values. 
15. Click the SAVE SETTINGS button. If a certificate warning is presented, click the ACCEPT button. Click the OK button on the confirmation dialogue. Click the CLOSE button.

Additional Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.