Following lines can be seen in logs.

/var/log/vmware/vmdir/vmafdvmdirclient.log

2019-03-27T22:46:12.297Z:t@139750577006336:ERROR: VmDirGeneratePassword failed (382312521)
2019-03-27T22:46:12.297Z:t@139750577006336:ERROR: VmDirLdapSetupComputerAccount (cn=vc.domain.local,ou=Computers,dc=domain,dc=local) failed with error (382312521)
2019-03-27T22:46:12.297Z:t@139750577006336:ERROR: VmDirClientJoin failed. Error(382312521)

/var/log/firstboot/vmafd-firstboot.py_XXXX_stderr.log

2019-03-27T22:46:12.298Z   AFD Join Domain Failed
2019-03-27T22:46:12.298Z
2019-03-27T22:46:12.298Z   password: Error 382312521: Failed to connect to the remote host, reason = rpc_s_host_unreachable (0x16c9a049).
2019-03-27T22:46:12.299Z   Exception: Traceback (most recent call last):
  File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 131, in main
    controller.client_mode()
  File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 79, in client_mode
    service.client_mode()
  File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmafdInstall.py", line 841, in client_mode
    self.join_domain()
  File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmafdInstall.py", line 412, in join_domain
    problemId = "install.vmafd.join_vmdir_failed")
BaseInstallException: {
    "resolution": {
        "id": "install.vmafd.join_vmdir_failed.resolution",
        "localized": "Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request.",
        "translatable": "Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request."
    },
    "detail": [
        {
            "args": [
                1
            ],
            "id": "install.vmafd.join_vmdir_failed",
            "localized": "ERROR: 1, join vmdir failed",
            "translatable": "ERROR: %(0)d, join vmdir failed"
        }

/var/log/firstboot/vmafd-firstboot.py_XXXX_stdout.log

2019-03-27T22:45:59.699Z   Starting service [vmafd]
Starting service [vmafd]
2019-03-27T22:45:59.699Z   Running command: ['systemctl', 'daemon-reload']
2019-03-27T22:45:59.784Z   Running command: ['systemctl', 'start', 'vmafdd']
2019-03-27T22:46:06.137Z   Running command: ['/opt/likewise/bin/lwsm', 'status', 'vmafd']
2019-03-27T22:46:06.149Z   running (standalone: 4654)
2019-03-27T22:46:06.149Z   Service [vmafd] started succesfully
2019-03-27T22:46:06.149Z   Getting VMWARE_JAVA_HOME from Env
2019-03-27T22:46:06.149Z   Admin Check Succeeded
2019-03-27T22:46:06.149Z   Setting domain name  domain.local
2019-03-27T22:46:06.190Z   Setting domain controller name psc1.domain.local
2019-03-27T22:46:06.222Z   Setting PNID vc1.domain.local
2019-03-27T22:46:06.254Z   Setting CA Path /etc/certs
2019-03-27T22:46:06.286Z   Running command: ['/usr/lib/vmware-vmafd/bin/vmafd-cli', 'join-vmdir', '--server-name', ' psc1.domain.local ', '--user-name', 'Administrator', '--machine-name', ' vc1.domain.local', '--domain-name', ‘domain.local']
2019-03-27T22:46:12.299Z   VMAFD Boot failed

This issue happens when vCenter is unable to connect PSC (previously) configured OR the DNS records (forward/reverse) of either PSC or vCenter isn’t configured correctly. In this situation, you can’t start vCenter services but the server can be accessed using SSH in configured during installation.

Using SSH take SSH to vCenter & PSC. Verify forward look up & reverse look up return correct results.

Forward lookup check.

root@vc1 []# nslookup vc1.domain.local
Name:   vc1.domain.local
Address: 10.121.1.79

Reverse lookup check

Whatever IP returns for vCenter in previous command use it for nslookup.

root@vc1 []# nslookup 10.121.1.79
Non-authoritative answer:
79.2.121.10.in-addr.arpa        name = vc1.domain.local.

This needs to done if you are using PSC externally.