A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/vmware/docker-volume-vsphere/issues/1914 below:

Volume gets created on incorrect vsan datastore. · Issue #1914 · vmware-archive/vsphere-storage-for-docker · GitHub

Testbed had a vsan datastore named - vsanDatastore

  1. Created a volume using long volume name - testX1@vsanDatastore
  2. Verified from docker cli and esxcli that volume was successfully created
  3. Tried creating another volume using incorrect datastore name - testX2@vsandatastore
    Remember that we do not have volume named vsandatastore. Even though we do not have any volume named vsandatastore, volume creation succeeded.
  4. Docker cli and esxcli also lists both the volumes are created on vsanDatastore.

So step 3 can be confusing to the user as even though the setup does not have a volume named vsandatastore, volumes creation succeeds.

So user is passing datastore name as vsandatastore whereas volume is getting created on vsanDatastore.

Logs have been attached at the end.

Detailed steps and their output are as follows:

  1. Created a volume using long volume name - testX1@vsanDatastore
root@sc-rdops-vm02-dhcp-52-237:~# docker volume create -d vsphere --name testX1@vsanDatastore
testX1@vsanDatastore
root@sc-rdops-vm02-dhcp-52-237:~#
  1. Verified from docker cli and esxcli that volume was successfully created
root@sc-rdops-vm02-dhcp-52-237:~# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      testX1@vsanDatastore
root@sc-rdops-vm02-dhcp-52-237:~#

[root@sc2-rdops-vm03-dhcp-106-33:~] esxcli storage guestvol volume ls
Volume  Datastore      VMGroup   Capacity  Used  Filesystem  Policy          Disk Format  Attached-to  Access      Attach-as               Created By    Created Date
------  -------------  --------  --------  ----  ----------  --------------  -----------  -----------  ----------  ----------------------  ------------  ------------------------
testX1  vsanDatastore  _DEFAULT  100MB     80MB  ext4        [VSAN default]  thin         detached     read-write  independent_persistent  ubuntu-VM0.2  Fri Sep 29 19:03:55 2017
[root@sc2-rdops-vm03-dhcp-106-33:~]
  1. Tried creating another volume using incorrect datastore name - testX2@vsandatastore . Volume creation succeeds even though there is no volume named vsandatastore .
root@sc-rdops-vm02-dhcp-52-237:~# docker volume create -d vsphere --name testX2@vsandatastore
testX2@vsandatastore
root@sc-rdops-vm02-dhcp-52-237:~#
  1. Docker cli and esxcli also lists both the volumes are created on vsanDatastore.
root@sc-rdops-vm02-dhcp-52-237:~# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      testX1@vsanDatastore
vsphere:latest      testX2@vsanDatastore     <<<<<<<<<< 
root@sc-rdops-vm02-dhcp-52-237:~#


[root@sc2-rdops-vm03-dhcp-106-33:~] esxcli storage guestvol volume ls
Volume  Datastore      VMGroup   Capacity  Used  Filesystem  Policy          Disk Format  Attached-to  Access      Attach-as               Created By    Created Date
------  -------------  --------  --------  ----  ----------  --------------  -----------  -----------  ----------  ----------------------  ------------  ------------------------
testX1  vsanDatastore  _DEFAULT  100MB     80MB  ext4        [VSAN default]  thin         detached     read-write  independent_persistent  ubuntu-VM0.2  Fri Sep 29 19:03:55 2017
testX2  vsanDatastore  _DEFAULT  100MB     80MB  ext4        [VSAN default]  thin         detached     read-write  independent_persistent  ubuntu-VM0.2  Fri Sep 29 19:04:22 2017
[root@sc2-rdops-vm03-dhcp-106-33:~]

Logs:
docker-volume-vsphere.txt
vmdk_ops.txt

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4