You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Note: having spaces in datastore name is a valid name in vc context; while adding ESXs to VC which is having same datastore name; VC renames datastore by appending '(N)' for later ESX automatically
Current result: volume creation is failing with following outcome
created volumes are not viewable so pulling into 0.12 release. If user happens to rename the datastore with embedded namespace, it will run into following issue.
using admin cli:
[root@sc-rdops-vm07-dhcp-193-230:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py ls
Invalid destination specification:
vmkfstools: (1)/dockvols/f7d20fb8-ead2-4327-ad6f-066c82a76930/dockerVol_1486430383.vmdk: No name specification expected.
Failed to stat /vmfs/volumes/vsanDatastore (1)/dockvols/f7d20fb8-ead2-4327-ad6f-066c82a76930/dockerVol_1486430383.vmdk. VMDK corrupted. Please remove and then retry
Steps to reproduce:
Expectation: volume creation should succeed
Note: having spaces in datastore name is a valid name in vc context; while adding ESXs to VC which is having same datastore name; VC renames datastore by appending '(N)' for later ESX automatically
Current result: volume creation is failing with following outcome
on ESX side:
The text was updated successfully, but these errors were encountered: