Issue 1:
I think yesterday they were running in under 40 minutes.

I did kubernetes-retired/contrib#1022 because the submit queue is timing out before merging after running tests. I will try to push it live tonight. But we need to figure out what caused this.

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): vsphere, lsilogic-sas

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report

Kubernetes version (use kubectl version): Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.5+coreos.0", GitCommit:"f70c2e5b2944cb5d622621a706bdec3d8a5a9c5e", GitTreeState:"clean", BuildDate:"2016-10-31T19:16:47Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: vSphere (vCenter: 6.5.0, ESXi: 6.0.0)

OS (e.g. from /etc/os-release): CoreOS 1185.3.0 (MoreOS)

Kernel (e.g. uname -a): Linux 4.7.3-coreos-r2 #1 SMP Tue Nov 1 01:38:43 UTC 2016 x86_64

Install tools:

Others:

What happened:

During pod provisioning, kube-controller-manager logged the following messages whilst attempting to attach a vSphere volume to the pod;

2016-11-27T14:15:01.636686228Z I1127 14:15:01.636561 1 reconciler.go:168] Started AttachVolume for volume "kubernetes.io/vsphere-volume/[DATASTORE] volumes/VOLUME" to node "NODE"
2016-11-27T14:15:02.085465901Z E1127 14:15:02.085346 1 vsphere.go:667] error creating new SCSI controller: unknown SCSI controller type 'lsiLogic-sas'
2016-11-27T14:15:02.102770470Z E1127 14:15:02.102592 1 attacher.go:79] Error attaching volume "[DATASTORE] volumes/VOLUME": unknown SCSI controller type 'lsiLogic-sas'
2016-11-27T14:15:02.102790243Z E1127 14:15:02.102691 1 nestedpendingoperations.go:253] Operation for "\"kubernetes.io/vsphere-volume/[DATASTORE] volumes/VOLUME\"" failed. No retries permitted until 2016-11-27 14:15:06.102667758 +0000 UTC (durationBeforeRetry 4s). Error: Failed to attach volume "VOLUME" on node "NODE" with: unknown SCSI controller type 'lsiLogic-sas'
2016-11-27T14:15:02.102908054Z I1127 14:15:02.102838 1 event.go:217] Event(api.ObjectReference{Kind:"Pod", Namespace:"default", Name:"mayan-deployment-2304867309-f4tgb", UID:"df9106ba-b4ab-11e6-b3bc-005056892975", APIVersion:"v1", ResourceVersion:"4951433", FieldPath:""}): type: 'Warning' reason: 'FailedMount' Failed to attach volume "VOLUME" on node "NODE" with: unknown SCSI controller type 'lsiLogic-sas'

The operation is attempted again and continues to fail. The pod becomes stuck in the ContainerCreating state.

What you expected to happen:

The volume should be mounted to the host and attached to the pod.

How to reproduce it (as minimally and precisely as possible):

Create a VMDK using the following command;

vmkfstools -c 2G /vmfs/volumes/DATASTORE/volumes/VOLUME.vmdk

Attach a vSphere volume to a pod using the following spec;

volumes:
- name: VOLUME
vsphereVolume:
volumePath: "[DATASTORE] volumes/VOLUME"
fsType: ext4

Anything else do we need to know:

This happens both with attaching an existing vSphere volume (as documented here) and with the vSphere StorageClass provisioner (as documented here). For the purposes of documenting this issue, I followed the former rather than the latter, but the error is the same.

Volume/datastore/host names have been substituted from their actual values.

The Kubernetes worker node's VM hardware is as follows;