-
Notifications
You must be signed in to change notification settings - Fork 95
New install unable to create and mount volumes #2048
Comments
@rsjorslev, can you post the SCSI controller configuration of the VM you are using to run the containers? Is there a pvscsi controller configured? If so can you post its configuration. |
Hi @govint, here is the full vmx from that VM:
|
scsi0 is the lsi controller added to the VM when it was created and scsi1 is the controller added by the driver. |
@rsjorslev, thanks for posting the VMX config, the logs don;t show a PVSCSI controller being added. Most likely the VIB was used earlier and volumes were created and used? The code seems to be unable to find the PVSCSI controller in the VMX extra-config (in the code) and hence None being used later. Suggest removing the disk and the PVSCSI controller manually from the VMX config and they retry the volume attach via docker. |
Just tried deleting the disk and pvscsi controller from the VM/VMX and then tried to create a new volume but got this:
it still seems to not find the controller - at least it looks like its always when it picks the first item in the array no matter the type of operation. |
@govint i Can provide remote access to the setup if required over zoom - just let me know. |
Debugged this yesterday and the root cause seems a bit strange where, the fields of the VM configuration - key names - are in lower case on the ESX 6.5 U1 host. Since the code is explicitly searching for a specific string. the search fails and a None value is returned for the scsi controller's slot and bus number fields. Will post the change for review today, |
I can confirm that the fix from @govint works as expected, i can now create, delete and mount volumes on 6.5 U1 environment. |
fixed through #2051 |
ESXi:
VMware ESXi, 6.5.0, 5969303 (SuperMicro Xeon-D system)
Datastore:
VMFS6, local SSD datastore (single host attached)
VM:
Ubuntu 16.04.03 (HW version 13 - also tried version 9 - same results) 2GB ram, 30GB VMDK for OS (LSI controller)
Docker version:
Server:
Engine:
Version: 17.12.0-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:09:53 2017
OS/Arch: linux/amd64
Experimental: false
VDVS Version:
[root@esx01:~] esxcli storage guestvol status
=== Service:
Version: 0.20.15f5e1d-0.0.1
Status: Running
Pid: 71845
Port: 1019
LogConfigFile: /etc/vmware/vmdkops/log_config.json
LogFile: /var/log/vmware/vmdk_ops.log
LogLevel: DEBUG
=== Authorization Config DB:
DB_SharedLocation: N/A
DB_LocalPath: N/A
DB_Mode: NotConfigured (no local DB, no symlink to shared DB)
Steps to Reproduce:
Fails with:
An actual VMDK file is created in dockvols under _DEFAULT
Fails with:
Triage:
vmdk_ops.log with DEBUG mode enabled:
The text was updated successfully, but these errors were encountered: