Failed to exit namespaces from maintenance mode due to Couldn't find WCP service end point.Retry 67Additional symptoms include:
The Enter Maintenance Mode task may become stuck.
Reconnecting the ESXi host might fail in the vSphere Client UI.
Executing enter or exit maintenance mode via esxcli or vim-cmd commands complete successfully.
VMware ESXi 8.0
This issue is caused by a DNS resolution failure.
During startup, vCenter Server services rely on proper DNS resolution — including self-resolution.
If no valid DNS server is configured, or if the /etc/hosts file has been modified (causing vCenter to lose self-resolution), service startup and communication with dependent components may fail. This results in abnormal vCenter behavior and maintenance mode errors.
To resolve the issue:
Configure a valid DNS server in your environment.
Set a proper hostname for vCenter Server via the VAMI UI.
Workaround:
If your vSphere environment does not have an active DNS server, perform the following steps:
SSH to the vCenter Server Appliance (VCSA).
Edit the /etc/hosts file and ensure it includes:
127.0.0.1 localhost.localdomain localhost
::1 localhost ipv6-localhost ipv6-loopback
<vCenter IP Address> localhostIf vCenter Server was installed using an IP address instead of a Fully Qualified Domain Name (FQDN), this issue is more likely to occur.
It is strongly recommended to use an FQDN and proper DNS configuration for stable vCenter Server operations.