vRealize Automation: Compute Resources Doesn’t Show During Fabric Groups Creation

VMware 1 Comment

A lot of things can cause this behavior, in my case, when I tried to create a Fabric Groups, the compute resources didn’t show!

The logs in vRealize Automation appliance (v7.0.1) show the following error in Infrastructure => Monitoring => Log:

This exception was caught: The attached endpoint 'vCenter' cannot be found.

The first thing I did was to reconfigure the credentials in Infrastructure => Endpoints => Credentials

vrealize automation credentials

Then I restarted the data collection manually. To do this go to  Infrastructure > Compute Resources > Compute Resources, point to the compute resources then Data collection.

vrealize data collection

 

On the Inventory, Click Request now

compute resource data collection

I still get the same error!

Then I checked the configuration on the Endpoints in  Infrastructure =>Endpoints => Endpoints, all was correct except one parameter! The Endpoint Name.

vsphere endpoint name

The Endpoint name must match the endpoint name provided during the vSphere proxy agent installation in your Iaas server.

You can get the configured endpoint name from the installed agent on your Iaas server in the C:\Program Files (x86)\VMware\vCAC\Agents\agentName, otherwise use the following command to get your current configuration:

C:\Program Files (x86)\VMware\vCAC\Agents\agentName\DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config get

get vsphere endpoint configuration

I changed the endpoint name in Infrastructure =>Endpoints => Endpoints and restarted the data collection, then everything worked smoothly.

 
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)

Loading...

One thought on “vRealize Automation: Compute Resources Doesn’t Show During Fabric Groups Creation

  • Zinny

    Hi

    Thanks for that update, Am getting the below error trying to register vRealize business standard to vRealize Automation center, Any ideas of what could be the issue? The credentials are correct.

    ERROR 2016-06-13 08:00:25.848 (ContextLoader .licationContext: 319) Context initialization failed
    org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name ‘systemDefaultTenantProvider’ defined in URL [file:/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/webapps/itfm-cloud/WEB-INF/classes/csp/plugin-config.xml]: Could not resolve placeholder ‘sso.tenant’ in string value “${sso.tenant}”

Leave a Reply

Your email address will not be published. Required fields are marked *