<p dir="auto">I think yesterday they were running in under 40 minutes.</p>
<p dir="auto">I did <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="155861384" data-permission-text="Title is private" data-url="https://github.com/kubernetes-retired/contrib/issues/1022" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes-retired/contrib/pull/1022/hovercard" href="https://github.com/kubernetes-retired/contrib/pull/1022">kubernetes-retired/contrib#1022</a> 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.</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.): vsphere, lsilogic-sas</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): Bug Report</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>): 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"}</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: vSphere (vCenter: 6.5.0, ESXi: 6.0.0)</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): CoreOS 1185.3.0 (MoreOS)</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux 4.7.3-coreos-r2 <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35192559" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/1" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/1/hovercard" href="https://github.com/kubernetes/kubernetes/issues/1">#1</a> SMP Tue Nov 1 01:38:43 UTC 2016 x86_64</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
During pod provisioning, kube-controller-manager logged the following messages whilst attempting to attach a vSphere volume to the pod;</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="2016-11-27T14:15:01.636686228Z I1127 14:15:01.636561       1 reconciler.go:168] Started AttachVolume for volume &quot;kubernetes.io/vsphere-volume/[DATASTORE] volumes/VOLUME&quot; to node &quot;NODE&quot;
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 &quot;[DATASTORE] volumes/VOLUME&quot;: unknown SCSI controller type 'lsiLogic-sas'
2016-11-27T14:15:02.102790243Z E1127 14:15:02.102691       1 nestedpendingoperations.go:253] Operation for &quot;\&quot;kubernetes.io/vsphere-volume/[DATASTORE] volumes/VOLUME\&quot;&quot; failed. No retries permitted until 2016-11-27 14:15:06.102667758 +0000 UTC (durationBeforeRetry 4s). Error: Failed to attach volume &quot;VOLUME&quot; on node &quot;NODE&quot; 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:&quot;Pod&quot;, Namespace:&quot;default&quot;, Name:&quot;mayan-deployment-2304867309-f4tgb&quot;, UID:&quot;df9106ba-b4ab-11e6-b3bc-005056892975&quot;, APIVersion:&quot;v1&quot;, ResourceVersion:&quot;4951433&quot;, FieldPath:&quot;&quot;}): type: 'Warning' reason: 'FailedMount' Failed to attach volume &quot;VOLUME&quot; on node &quot;NODE&quot; with: unknown SCSI controller type 'lsiLogic-sas'"><pre class="notranslate"><code class="notranslate">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'
</code></pre></div>
<p dir="auto">The operation is attempted again and continues to fail. The pod becomes stuck in the ContainerCreating state.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
The volume should be mounted to the host and attached to the pod.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<ol dir="auto">
<li>Create a VMDK using the following command;</li>
</ol>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="vmkfstools -c 2G /vmfs/volumes/DATASTORE/volumes/VOLUME.vmdk"><pre class="notranslate"><code class="notranslate">vmkfstools -c 2G /vmfs/volumes/DATASTORE/volumes/VOLUME.vmdk
</code></pre></div>
<ol start="2" dir="auto">
<li>Attach a vSphere volume to a pod using the following spec;</li>
</ol>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="      volumes:
        - name: VOLUME
          vsphereVolume:
            volumePath: &quot;[DATASTORE] volumes/VOLUME&quot;
            fsType: ext4"><pre class="notranslate"><code class="notranslate">      volumes:
        - name: VOLUME
          vsphereVolume:
            volumePath: "[DATASTORE] volumes/VOLUME"
            fsType: ext4
</code></pre></div>
<p dir="auto"><strong>Anything else do we need to know</strong>:<br>
This happens both with attaching an existing vSphere volume (as documented <a href="http://kubernetes.io/docs/user-guide/volumes/#vspherevolume" rel="nofollow">here</a>) and with the vSphere StorageClass provisioner (as documented <a href="http://kubernetes.io/docs/user-guide/persistent-volumes/#vsphere" rel="nofollow">here</a>). For the purposes of documenting this issue, I followed the former rather than the latter, but the error is the same.<br>
Volume/datastore/host names have been substituted from their actual values.<br>
The Kubernetes worker node's VM hardware is as follows;<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/6966796/20649056/3dbc5894-b4ae-11e6-8830-51bb61b45eac.png"><img src="https://cloud.githubusercontent.com/assets/6966796/20649056/3dbc5894-b4ae-11e6-8830-51bb61b45eac.png" alt="image" style="max-width: 100%;"></a></p>