This is a known issue affecting VMware vRealize Automation versions 7.3, 7.3.1, and 7.4.
Currently, there is no resolution.
Workaround:
To work around this issue:
- In the domains where the primary domain controller fails, open the /usr/local/horizon/conf/domain_krb.properties file and replace the value of the failed domain controller with the value of a secondary domain controller.
- Check whether the failed domain controller is present in any of the config-state.json files present in the /usr/local/horizon/conf/states/tenant_name/ directory.
- If the failed domain controller is present, replace the failed domain controller name with the name of the secondary domain controller.
- Restart the virtual appliance.