VMware is aware of this issue and working to resolve this in a future release.
Workaround:
To work around this issue, use one of these options:
- Use alternate transport mode like nbd, ndbssl, and hotadd instead of SAN transport mode
- If using SAN transport mode is mandatory, try connecting directly to ESX/ESXi host instead of vCenter server.
- Use thick provision type if you want to use SAN mode.