No tenants visible when running SovLabs Configuration workflow or when using vsphere.local as your default tenant

Problem 

After you have installed the SovLabs module into vRO and you run the SovLabs Configuration workflow.  You are unable to select a Tenant or Business group as these appear to be empty.

Cause

1. You have not configured any vRA hosts or IaaS Hosts as part of the Pre Requisites (Please follow the steps outlined in the Additional Information at the bottom of this page)
2. If you have setup your environment to utilise the default vsphere.local tenant but have not configured your vRA host name to have "sovlabs_" in front of the host name.  

This is outlined in step 2.3 of the SovLabs pre requisite documentation.

http://docs.sovlabs.com/latest/vRA/7.6/getting-started/configure-vro/step-2-3/#create-vro-vra-host

Example of incorrect configuration running from vRO (Library → vRealize Automation → Configuration → Add a vRA host)

Affected Versions

• All SovLabs Module versions

• All vRA versions

Solution

Overview

To resolve this issue, you will have to do the following:

• Delete incorrectly named vRA host
• Delete the associated IaaS host
• Create a new vRA host with sovlabs_ infront
• Create a new IaaS host associated to your newly create vRA host

Removing the vRA host with incorrect information

1. Within the vRO client, Change to Design view (1), Click on Workflows (2) and then go to Library → vRealize Automation → Configuration → Remove a vRA host (3)
   1. 
2. Run the workflow of Remove a vRA host
   1. 
3. Click on Not set under vCloud automation Center host to remove
   1. 
4. On the left side, drop down the list (1) so you can see the host you want to remove then highlight the host (2).  Click on Select (3)
   1. 
5. Click on Submit
   1. 
6. Confirm the job has run but looking under the workflow of Remove a vRA host
   1. 
7. Click on Inventory across the top menu
   1. 
8. Click on Refresh at the top
   1. 
9. Now expand on the left vRealize Automation and check that the vRA host you removed is no longer visible
   1. 

Removing the IaaS host associated with the incorrectly configured vRA host

1. In vRO click on Library → vRealize Automation → Infrastructure Administrator → Configuration → Remove an IaaS host
   1. 
2. Run this workflow
   1. 
3. Click on Not Set under vCloud Automation Center host to remove
   1. 
4. Drop down on the left to see your IaaS hosts (1) and select the one you wish to remove (2) then click select (3)
   1. 
5. Click on Submit
   1. 
6. Confirm the workflow completed successfully
   1. 
7. Across the top menu click on Inventory
   1. 
8. At the top, click on refresh
   1. 
9. On the left drop down on vRealize Automation Infrastructure and confirm the IaaS host has been removed
   1. 

Adding in the vRA host with sovlabs_ as the name for the vsphere.local tenant

You will be following the steps as outline in 2.3 (http://docs.sovlabs.com/latest/vRA/7.6/getting-started/configure-vro/step-2-3/#create-vro-vra-host) to create the host

1. In vRO, go to Library → vRealize Automation → Configuration → Add a vRA host
   1. 
2. Run this workflow
   1. 
3. In Host Name, Enter the host with sovlabs_ in front (1) , The host URL, enter without sovlabs_ in front (2), Select Yes for SSL certificates (3), Leave the rest as defaults (4) and click Next
   1. 
4. In session mode select Shared Session (1), in Tenant, enter vsphere.local (2), Authentication username the sov_admin@vsphere.local (Or other nominated account for your environment) along with the password (3) then click Submit (4)
   1. 
5. Confirm the host has added succesfully and that in the logs it shows the host VALUE: sovlabs_<vrahostservername>, <HOSTNAME>[vsphere.local]
   1. 
   2. 
6. In the top menu, select Inventory
   1. 
7. At the top, click on refrest
   1. 
8. On the left side, click on vRealize Automation drop down and look for your newly added host. This host will begin with sovlabs_
   1. 

Adding in the vRA IaaS host for the vsphere.local tenant

You will be following the steps as outline in 2.4 (http://docs.sovlabs.com/latest/vRA/7.6/getting-started/configure-vro/step-2-4/#create-vro-vra-iaas-host) create vRO vRA IaaS  host

1. In vRO, go to Library → vRealize Automation → Configuration → Add the IaaS host of a vRA host
   1. 
2. Run this workflow
   1. 
3. Under vCAC host, click on Not Set
   1. 
4. Drop down on vRealize Automation (1) and locate the sovlabs_<VRAHOST> (2), click on this and then click on Select (3)
   1. 
5. Click on Next
   1. 
6. This should auto populate the URL and servers for IaaS services, click on Next
   1. 
7. Leave defaults unless you are using a proxy, click on Next
   1. 
8. You should select SSO as the default type for the internal vRO and click on Submit. 
   NOTE: If you are setting up an external vRO and using vsphere.loca the SovLabs Configuration will fail.  You must create a new tenant for External VRO use
   1. 
      
9. Confirm your workflow has run succesfully
   1. 
10. Click on Inventory in the top menu
    1. 
11. Click on Refresh at the top of the screen
    1. 
12. Drop down the vRealize Automation Infrastructure and look for the IaaS host you created, if you left the default name, it would start with "IaaS host for sovlabs_<HOSTNAME>[https://<vraserver>]
    1. 

Additional information

Create a vRO / vRA Host:  http://docs.sovlabs.com/latest/vRA/7.6/getting-started/configure-vro/step-2-3/#create-vro-vra-host

Create a vRO / vRA IaaS Host: http://docs.sovlabs.com/latest/vRA/7.6/getting-started/configure-vro/step-2-4/#create-vro-vra-iaas-host