OTV Datastore Mount Operation Completes but Datastore Is Not Visible on Target ESXi Hosts

Applies to

• ONTAP Tools for VMware vSphere (OTV) 10.X
• Environments using OTV with cross-cluster datastore mounts

Issue

• Attempts to mount an existing datastore to additional ESXi hosts or clusters using ONTAP Tools for VMware vSphere (OTV) complete successfully, but the datastore does not become visible on the target ESXi hosts.

  Symptoms include:

  • The OTV mount job may complete without reporting a failure.
  • The datastore does not become visible on the target ESXi hosts.
  • Manual LUN mapping outside of OTV succeeds.

 OTV log output:

2026-06-23T06:40:16.982682876Z stdoutF { "file":"/app/datastore-service/service/datastore.go:1053", "jobId":"35478", "level":"error", "message":"container vcguid does not match with the vcguid passed in the context", ... }
2026-06-23T06:40:16.987402551Z stdoutF { "file":"/app/datastore-service/endpoint/datastore.go:359", "jobId":"35478", "level":"error", "message":"InvalidRequest. Incorrect container uuid passed", ... }

Additional details:

• In the affected environment, the DR vCenter instanceUuid (vcguid) was stored in uppercase format, whereas the Production vCenter instanceUuid was stored in lowercase format.
  
• The instanceUuid format can be verified on the vCenter Server using the following commands:

PROD vCenter

root@VC01 [ ~ ]# sudo cat /etc/vmware-vpx/instance.cfg | grep instanceUuid
instanceUuid=45d7jglc6-9d1f-43b9-9bdq-8dfdjh9bed0
root@VC01 [ ~ ]# sudo cat /etc/vmware-vpx/firstboot/vpxd-service-spec.prop | grep cmreg.serviceid
cmreg.serviceid=45d7jglc6-9d1f-43b9-9bdq-8dfdjh9bed0

DR vCenter

root@VC02 [ ~ ]# sudo cat /etc/vmware-vpx/instance.cfg | grep instanceUuid
instanceUuid=5454B4F-42T5-445V-A89K-DA7D1B5DE2GT
root@VC02 [ ~ ]# sudo cat /etc/vmware-vpx/firstboot/vpxd-service-spec.prop | grep cmreg.serviceid
cmreg.serviceid=5454B4F-42T5-445V-A89K-DA7D1B5DE2GT