Need to add more verification steps for basic_test

[shuklanirdesh82]

CI run: https://ci.vmware.run/vmware/docker-volume-vsphere/648

=== RUN   Test
2017/06/21 08:09:31 START: BasicTestSuite.TestBasicVolumeIsolation
2017/06/21 08:09:31 Creating volume [BasicTestSuite.TestBasicVolumeIsolation_volume_16ddfwutxgjte] on VM [192.168.31.81]
2017/06/21 08:09:42 Checking volume [BasicTestSuite.TestBasicVolumeIsolation_volume_16ddfwutxgjte] availability from VM [192.168.31.81]
2017/06/21 08:09:42 Checking volume [BasicTestSuite.TestBasicVolumeIsolation_volume_16ddfwutxgjte] availability from VM [192.168.31.85]
2017/06/21 08:09:43 Destroying volume [BasicTestSuite.TestBasicVolumeIsolation_volume_16ddfwutxgjte]
2017/06/21 08:09:45 END: BasicTestSuite.TestBasicVolumeIsolation
2017/06/21 08:09:45 START: BasicTestSuite.TestVmGroupVolumeIsolation
2017/06/21 08:09:45 Initializing the SingleNode Config DB on esx [192.168.31.62] 
2017/06/21 08:09:47 Creating volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz] on VM [192.168.31.81]
2017/06/21 08:09:55 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz] availability from VM [192.168.31.81]
2017/06/21 08:09:56 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz] availability from VM [192.168.31.85]
2017/06/21 08:09:56 Creating a vmgroup [T1] on esx [192.168.31.62]
2017/06/21 08:09:59 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz] availability from VM [192.168.31.81]
2017/06/21 08:09:59 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz] availability from VM [192.168.31.85]
2017/06/21 08:10:00 Creating volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_tr8b5apa57f5] on VM [192.168.31.81]
2017/06/21 08:10:07 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_tr8b5apa57f5] availability from VM [192.168.31.81]
2017/06/21 08:10:08 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_tr8b5apa57f5] availability from VM [192.168.31.85]
2017/06/21 08:10:08 Destroying volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_uo7w8oxnzncz]
2017/06/21 08:10:10 Destroying volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_tr8b5apa57f5]
2017/06/21 08:10:12 Removing the SingleNode Config DB on esx [192.168.31.62] 
2017/06/21 08:10:14 END: BasicTestSuite.TestVmGroupVolumeIsolation
::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::::::::::::::::::::::::::::::::::::::::::::::::::::::
2017/06/21 08:11:06 START: VolumeAccessTestSuite.TestAccessUpdate
2017/06/21 08:11:06 Creating volume [vol_access_volume_l33x03nwf9uh@datastore1] on VM [192.168.31.81]
2017/06/21 08:11:13 Writing message_by_host1 to file test.txt on volume [vol_access_volume_l33x03nwf9uh@datastore1] from VM[192.168.31.81]
2017/06/21 08:11:18 Reading from file test.txt on volume [vol_access_volume_l33x03nwf9uh@datastore1] from VM[192.168.31.85]
2017/06/21 08:11:19 Destroying volume [vol_access_volume_l33x03nwf9uh@datastore1]
2017/06/21 08:11:20 START: VolumeAccessTestSuite.TestAccessUpdate_R_RW
2017/06/21 08:11:20 Creating volume [vol_access_volume_f0iszigydzxy@datastore1] with options [ -o access=read-only] on VM [192.168.31.81]

----------------------------------------------------------------------
FAIL: volume_access_test.go:76: VolumeAccessTestSuite.TestAccessUpdate

volume_access_test.go:91:
    c.Assert(err, IsNil, Commentf(out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc4201199e0), Stderr:[]uint8(nil)} ("exit status 125")
... docker: Error response from daemon: create vol_access_volume_l33x03nwf9uh@datastore1: "vol_access_volume_l33x03nwf9uh@datastore1" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.

The above failure message doesn't help at all to reach root cause easily. It could have been simpler by having more verification steps following to any operation using admin cli.

By looking at the above failure it leads to volume_test failure in fact it is a victim of leftover remnants from basic_test.

[shuklanirdesh82]

Reference: #1401 (comment)

would have opened as P1, #1401 is under review it would be better to address this issue sooner so keeping as P0.

/CC @msterin