Hi all,
We are having problems instantiating an IWA Active Directory on a third tenant in vRA 7.0.1, which uses the same settings we set on the previous two. Our tenants are as follows:
1. vsphere.local (Default Tenant)
2. POC Tenant A
3. POC Tenant B
We created the the AD bindings on both the Default Tenant and POC Tenant A with the same values. They have the same Directory Name, Sync Connector, Authentication, Directory Search Attribute, and Bind Details. Both the Default Tenant and POC Tenant A are syncing to AD properly and users can interact with the product using their native AD accounts and groups.
We then created POC Tenant B and tried to setup the directory with the same settings. Prior to this, no configurations were made against POC Tenant B. After clicking submit, we receive the error "Unable to Activate the Connector." We clicked cancel, looked at the Identity Providers tab and saw that nothing was created. We then went into the Connectors tab and saw that there is a Connector in place, but it only lists out the host name value (which matches Default Tenant and Tenant A) but it doesn't have a worker, IP, Auth method, etc populated. We then tried to recreate the directory again, but under a different name. The first time we did this, it created the directory object but did not fully instantiate the IDP. We attempted to change the IDP to match the settings of the other two tenants, but doing so made both the IDP and the Directory object disappear from the GUI. Now, anytime we click the Directories tab on Tenant B we receive a "Internal Server Error" banner. Now anytime we try creating the directory, we receive the "Unable to Activate the Connector" error.
To me, it seems like there is some kind of contention issue in the Postgres. I'm thinking it's trying to create the same IDP and Connector but is trying to use the same values and is throwing some kind of Primary Key violation. I tried looking at the various logs in /var/log/vmware/horizon on the appliance, but haven't really found anything that strikes out.
Has anyone experience this issue before?