vRealize Automation logon issue

[jwyrwinski]

Dear Community Members,

I recently deployed new vRealize Automation 7 appliance. I have succesfully  completed initial configuration over the wizard. This is simple PoC configuration with single vRA and IaaS server build on W2k12 R2 w/h MS SQL 2012.

I cannot logon to Automation Console (https://vra_appliance_name.domain/vcac) with the credentials I have configured for configurationadmin account during the wizard. The circle is spinning around all the time. I have redeployed vRA Appliance twice but with no luck. I did not upload the license key as I do not have any yet, so there is a simple popup message saing that license is not available but I am pretty sure it's not the case.

All services seem to be started except "com.vmware.csp.iaas.blueprint.service" which does not have status defined.

I have found following error message in the vcac-config.log file:

2016-01-27T13:23:22.386033+00:00 vRA vcac-config: INFO  com.vmware.vcac.cli.configurator.services.cluster.impl.ClusterNodeCommunicatorImpl.getVraInternalPort:485 - Processing nodes, found by expression /Server/Service/Connector[@address='localhost']...

2016-01-27T13:23:22.404860+00:00 vRA vcac-config: INFO  com.vmware.vcac.cli.configurator.services.cluster.impl.ClusterNodeCommunicatorImpl.waitUntilCurrentNodeIsAvailable:397 - Checking status for current node: http://127.0.0.1:8082/vcac/services/api/health

2016-01-27T13:23:22.414982+00:00 vRA vcac-config: INFO  com.vmware.vcac.cli.configurator.services.cluster.impl.ClusterNodeCommunicatorImpl.isCurrentNodeAvailable:374 - Checking status for http://127.0.0.1:8082/vcac/services/api/health...

2016-01-27T13:23:23.222570+00:00 vRA vcac-config: INFO  com.vmware.vcac.cli.configurator.services.cluster.impl.ClusterNodeCommunicatorImpl.isCurrentNodeAvailable:382 - Node unavailable. Error: [http://127.0.0.1:8082/vcac/services/api/health, 404 Not Found]

2016-01-27T13:23:23.222997+00:00 vRA vcac-config: WARN  com.vmware.vcac.platform.rest.client.support.RetriableOperation.call:74 - Exception handled during retry operation with message: Current node is not available.

2016-01-27T13:23:23.223313+00:00 vRA vcac-config: INFO  com.vmware.vcac.platform.rest.client.support.RetriableOperation.call:76 - Retries left: [59]. Sleeping for [30] seconds before the next retry attempt.

2016-01-27T13:23:25.349085+00:00 vRA vcac-config: INFO  com.vmware.vcac.platform.ext.Configuration.loadMetricsProperties:98 - load metrics properties is done

Does anyone of you has met this issue before?

[GrantOrchardVMw]

Those 404s do suggest that the services haven't all come up yet. It may be that they don't until a license is applied.

Can you login as administrator@vsphere.local?

Grant

[jwyrwinski]

Hi Grant,

I have tried before but with no success.

When I login to vRA appliance at https://vra.domain:5480 as a root, there is no status displayed for iaas-service. When I login at https://vra:5480, status of iaas-service is given as a registered. However, logon to https://vra.domain/vcac still does not work.

[it10]

hi, i'm in the same boat on this one.  Redone the entire thing twice now (version 7) and still can't log in.

[it10]

i got in on mine.  it's no longer administrator@vsphere.local, you have to log in as just administrator.  

[jwyrwinski]

Both seems not to work, administrator as well as administrator@vsphere.local

It lets me in when I type correct credentials, it does not let me in with wrong credentials, so SSO seems to work properly. However, the portal does not display.

Can it be related to lack of license applied on VRA appliance?

[wsyed]

Yes, it is related to license keys applied, didn't apply any license and getting below screen..