Hello
I am looking for advice from those with install experience of iaas in vCAC and vRA.
I had a problem with the iaas-service showing as blank and not REGISTERED in the appliance (it did work previously)
I went through the routine of replacing certificates (self signed as this is a POC in a lab) which unfortunately hasn't resolved. I have did this again replacing all certs from the identity appliance / vRA appliance and the IIS certs as well (still no good)
I did have a problem with the vco service but managed to resolve that. I attach a screenshot. is there anything else I can try or something in the logs i should be looking for. Open to any suggestions. Is it worth redeploying the vRA appliance and getting the other components to trust that or am i better starting all over again (which i would love to avoid).
Any help greatly appreciated
Will
Can you confirm that you ran the following commands as part of the cert replacement process?
vcac-config.exe RegisterEndpoint --EndpointAddress https://IaaS_fqdn/vcac --Endpoint ui -v
vcac-config.exe RegisterEndpoint --EndpointAddress https://IaaS_fqdn/repository --Endpoint repo -v
vcac-config.exe RegisterEndpoint --EndpointAddress https://IaaS_fqdn/WAPI --Endpoint wapi -v
vcac-config.exe RegisterEndpoint --EndpointAddress https://IaaS_fqdn/WAPI/api/status --Endpoint -v
Grant
Hi grant
I can confirm i ran those commands yes
I even re-did the whole process twice more from scratch following every step. I guess i need to start again?
Can you check Repository Logs. Which will have some information behind the failure.
so i checked the logs and they are below but its still showing as blank. am i missing something from this output?
[UTC:2015-02-25 13:10:14 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 40 - Setting CafeClientCacheDuration: 00:05:00
[UTC:2015-02-25 13:10:14 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 40 - (1) GET endpoints/types/sso
[UTC:2015-02-25 13:10:15 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 35 - (1) Response: OK
[UTC:2015-02-25 13:10:15 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 35 - (2) GET endpoints/types/com.vmware.csp.cafe.authorization.api/default
[UTC:2015-02-25 13:10:17 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 36 - (2) Response: OK
[UTC:2015-02-25 13:10:17 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 40 - (3) GET endpoints/types/com.vmware.csp.cafe.authentication.api/default
[UTC:2015-02-25 13:10:17 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 35 - (3) Response: OK
[UTC:2015-02-25 13:10:17 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 40 - (4) GET tenants/vsphere.local/scopes/
[UTC:2015-02-25 13:10:19 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 36 - (4) Response: OK
[UTC:2015-02-25 13:10:19 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 40 - (5) GET tenants/vsphere.local/scopes/
[UTC:2015-02-25 13:10:19 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 35 - (5) Response: OK
[UTC:2015-02-25 13:10:51 Local:2015-02-25 13:10] [Info]: Thread-Id: 35 - Model MetaModel service has been initialized.
[UTC:2015-02-25 13:10:51 Local:2015-02-25 13:10] [Info]: Thread-Id: 41 - Model TrackingModel service has been initialized.
[UTC:2015-02-25 13:10:52 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 36 - (6) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:10:54 Local:2015-02-25 13:10] [VMware.Cafe]: Thread-Id: 9 - (6) Response: OK
[UTC:2015-02-25 13:11:17 Local:2015-02-25 13:11] [Debug]: Thread-Id: 41 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 15
[UTC:2015-02-25 13:11:53 Local:2015-02-25 13:11] [Info]: Thread-Id: 36 - Model ManagementModelEntities service has been initialized.
[UTC:2015-02-25 13:11:54 Local:2015-02-25 13:11] [VMware.Cafe]: Thread-Id: 34 - (7) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:12:09 Local:2015-02-25 13:12] [VMware.Cafe]: Thread-Id: 5 - (7) Response: OK
[UTC:2015-02-25 13:12:54 Local:2015-02-25 13:12] [VMware.Cafe]: Thread-Id: 35 - (8) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:12:55 Local:2015-02-25 13:12] [VMware.Cafe]: Thread-Id: 11 - (8) Response: OK
[UTC:2015-02-25 13:13:55 Local:2015-02-25 13:13] [VMware.Cafe]: Thread-Id: 38 - (9) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:13:56 Local:2015-02-25 13:13] [VMware.Cafe]: Thread-Id: 34 - (9) Response: OK
[UTC:2015-02-25 13:14:56 Local:2015-02-25 13:14] [VMware.Cafe]: Thread-Id: 38 - (10) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:14:56 Local:2015-02-25 13:14] [VMware.Cafe]: Thread-Id: 10 - (10) Response: OK
[UTC:2015-02-25 13:15:38 Local:2015-02-25 13:15] [Info]: Thread-Id: 38 - Model UcsModelEntities service has been initialized.
[UTC:2015-02-25 13:15:57 Local:2015-02-25 13:15] [VMware.Cafe]: Thread-Id: 38 - (11) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:15:57 Local:2015-02-25 13:15] [VMware.Cafe]: Thread-Id: 22 - (11) Response: OK
[UTC:2015-02-25 13:16:57 Local:2015-02-25 13:16] [VMware.Cafe]: Thread-Id: 39 - (12) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:16:57 Local:2015-02-25 13:16] [VMware.Cafe]: Thread-Id: 11 - (12) Response: OK
[UTC:2015-02-25 13:17:58 Local:2015-02-25 13:17] [VMware.Cafe]: Thread-Id: 39 - (13) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:17:58 Local:2015-02-25 13:17] [VMware.Cafe]: Thread-Id: 10 - (13) Response: OK
[UTC:2015-02-25 13:18:58 Local:2015-02-25 13:18] [VMware.Cafe]: Thread-Id: 5 - (14) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:18:58 Local:2015-02-25 13:18] [VMware.Cafe]: Thread-Id: 27 - (14) Response: OK
[UTC:2015-02-25 13:19:59 Local:2015-02-25 13:19] [VMware.Cafe]: Thread-Id: 5 - (15) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:19:59 Local:2015-02-25 13:19] [VMware.Cafe]: Thread-Id: 38 - (15) Response: OK
[UTC:2015-02-25 13:20:59 Local:2015-02-25 13:20] [VMware.Cafe]: Thread-Id: 11 - (16) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:20:59 Local:2015-02-25 13:20] [VMware.Cafe]: Thread-Id: 35 - (16) Response: OK
[UTC:2015-02-25 13:21:59 Local:2015-02-25 13:21] [VMware.Cafe]: Thread-Id: 11 - (17) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:22:00 Local:2015-02-25 13:22] [VMware.Cafe]: Thread-Id: 35 - (17) Response: OK
[UTC:2015-02-25 13:22:29 Local:2015-02-25 13:22] [Trace]: Thread-Id: 19 - String :<?xml version="1.0" encoding="utf-16"?>
<string />
[UTC:2015-02-25 13:23:00 Local:2015-02-25 13:23] [VMware.Cafe]: Thread-Id: 38 - (18) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:23:01 Local:2015-02-25 13:23] [VMware.Cafe]: Thread-Id: 34 - (18) Response: OK
[UTC:2015-02-25 13:24:01 Local:2015-02-25 13:24] [VMware.Cafe]: Thread-Id: 34 - (19) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:24:01 Local:2015-02-25 13:24] [VMware.Cafe]: Thread-Id: 5 - (19) Response: OK
[UTC:2015-02-25 13:24:11 Local:2015-02-25 13:24] [Debug]: Thread-Id: 34 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 4
[UTC:2015-02-25 13:25:01 Local:2015-02-25 13:25] [VMware.Cafe]: Thread-Id: 10 - (20) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:25:02 Local:2015-02-25 13:25] [VMware.Cafe]: Thread-Id: 11 - (20) Response: OK
[UTC:2015-02-25 13:26:02 Local:2015-02-25 13:26] [VMware.Cafe]: Thread-Id: 8 - (21) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:26:02 Local:2015-02-25 13:26] [VMware.Cafe]: Thread-Id: 11 - (21) Response: OK
[UTC:2015-02-25 13:26:41 Local:2015-02-25 13:26] [Info]: Thread-Id: 8 - Model CoreModel service has been initialized.
[UTC:2015-02-25 13:27:03 Local:2015-02-25 13:27] [VMware.Cafe]: Thread-Id: 8 - (22) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:27:03 Local:2015-02-25 13:27] [VMware.Cafe]: Thread-Id: 19 - (22) Response: OK
[UTC:2015-02-25 13:27:38 Local:2015-02-25 13:27] [Debug]: Thread-Id: 9 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 3
[UTC:2015-02-25 13:28:03 Local:2015-02-25 13:28] [VMware.Cafe]: Thread-Id: 19 - (23) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:28:03 Local:2015-02-25 13:28] [VMware.Cafe]: Thread-Id: 26 - (23) Response: OK
[UTC:2015-02-25 13:29:04 Local:2015-02-25 13:29] [VMware.Cafe]: Thread-Id: 19 - (24) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:29:04 Local:2015-02-25 13:29] [VMware.Cafe]: Thread-Id: 22 - (24) Response: OK
[UTC:2015-02-25 13:30:04 Local:2015-02-25 13:30] [VMware.Cafe]: Thread-Id: 36 - (25) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:30:04 Local:2015-02-25 13:30] [VMware.Cafe]: Thread-Id: 19 - (25) Response: OK
[UTC:2015-02-25 13:31:05 Local:2015-02-25 13:31] [VMware.Cafe]: Thread-Id: 11 - (26) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:31:05 Local:2015-02-25 13:31] [VMware.Cafe]: Thread-Id: 22 - (26) Response: OK
[UTC:2015-02-25 13:31:20 Local:2015-02-25 13:31] [Debug]: Thread-Id: 39 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 1
[UTC:2015-02-25 13:32:05 Local:2015-02-25 13:32] [VMware.Cafe]: Thread-Id: 39 - (27) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:32:05 Local:2015-02-25 13:32] [VMware.Cafe]: Thread-Id: 45 - (27) Response: OK
[UTC:2015-02-25 13:32:19 Local:2015-02-25 13:32] [Debug]: Thread-Id: 21 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 1
[UTC:2015-02-25 13:33:06 Local:2015-02-25 13:33] [VMware.Cafe]: Thread-Id: 44 - (28) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:33:06 Local:2015-02-25 13:33] [VMware.Cafe]: Thread-Id: 46 - (28) Response: OK
[UTC:2015-02-25 13:33:18 Local:2015-02-25 13:33] [Debug]: Thread-Id: 47 - DEM Claim Instances: DEM Id: 1 Session Id: fa08a7a8-e323-4508-9b52-32be069ebc00 Claimed instances: 1
[UTC:2015-02-25 13:34:06 Local:2015-02-25 13:34] [VMware.Cafe]: Thread-Id: 44 - (29) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:34:07 Local:2015-02-25 13:34] [VMware.Cafe]: Thread-Id: 46 - (29) Response: OK
[UTC:2015-02-25 13:35:07 Local:2015-02-25 13:35] [VMware.Cafe]: Thread-Id: 50 - (30) PUT tenants/vsphere.local/authorities/extended/permissions
[UTC:2015-02-25 13:35:08 Local:2015-02-25 13:35] [VMware.Cafe]: Thread-Id: 54 - (30) Response: OK
looks like Repository is working fine. Can you try https//<IAAS IP>/WAPI/api/status and see are there any errors over there?
screenshot attached
still shows blank on the vRA appliance tho
Everything looks perfect. Connectivity from VCAC VA and IAAS machine are fine? I mean are you able to ping the machine using FQDN?
certainly can ping the FQDN both ways
no firewalls in place
I appreciate your help and in a way i am glad this is puzzling as I have read many articles and tried very hard to resolve this without success
I did have the logs complain about FIPs but I disabled this in the registry and the logs stopped complaining about it
is there anything else i can check or am i looking at a rebuild from scratch?
hey did you try to re-initialize the SSO integration once again and eventually reboot the complete stack...it happened to me and i got it working when i could re-initialize the SSO in vCAC appliance.
Also a Dumb advice , try cleaning up Browser Cache and check it helps as well sometime
Br,
MG
Even i suggest to restart the appliance or vcac-server once. Actually re-initialize sso does restart of services so you can try it out.
thanks both I will try the above today and report back my findings
Did you have any luck fixing this error?
afraid not. went through the pain of re-installing as managed to get it working that way
FYI.... I had the same problem and it ended up being the account the Application Pools were using. Once I updated the account/password (was the same but just re-entered them) it started working again.