Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
vSAN File service domain creation failed with a timeout or a task failed for an unknown reason.In the /var/log/vsanfs.mgmt.log file, you see entries similar to: 2020-06-25T12:55:47.943Z error [EndpointController-2] [Create] Warning: failed to create container Traceback (most recent call last): File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/api/client.py", line 222, in _raise_for_status File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/requests/models.py", line 929, in raise_for_status requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: http+docker://localunixsocket/v1.30/containers/2f963ea053c88e678d49f4e8a51a9269fd3d9084b45a8b7d4035c3e8a6b35bf4/start During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/VDFSEndpointContainerDocker.py", line 120, in Create File "/build/m ts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/models/containers.py", line 337, in start File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/utils/decorators.py", line 19, in wrapped File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/api/container.py", line 1086, in start File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/api/client.py", line 224, in _raise_for_status File "/build/mts/release/bora-16410008/bora/build/esx/release/vdfs/usr/lib/vmware/vsan/perfsvc/docker/errors.py", line 31, in create_api_error_from_http_exception docker.errors.APIError: 403 Client Error: Forbidden ("Address already in use") Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This article provides information on a possible misconfiguration with the VSAN product.
This issue occurs as the IP address in the IP configuration provided for the VSAN File services are already in use.
This is a known issue affecting VMware ESXi 7.0.x.Currently, there is no resolution.
To work around this issue, clean-up the existing vSAN File service configuration and create the file service domain again with an alternate IP addresses which are not in use.Note: It is recommended to perform this procedure only under the guidance of VMware Technical Support. Contact VMware Support and reference this Knowledge Base article (80751) in the problem description of your support request. For more information, see How to File a Support Request .