Symptoms
This issue occurs when publishing vCenter is unable to connect to the other vCenter through the proxy server.
To work around this issue, edit the NO_PROXY section in /etc/sysconfig/proxy to include the other vCenter Servers domain, as recommended in https://knowledge.broadcom.com/external/article/370265/how-to-configure-proxy-settings-for-vcen.html
..
# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY="localhost, 127.0.0.1, vc.domain.tld, 192.168.1.55"
..
# service-control --stop --all && service-control --start --all