smbplugin.exe resulting in Windows nodes and causing blue screens

[WangMosquito]

What happened:
Working for one to two days on Windows systems a blue screen occurs .

What you expected to happen:
SMB mounts can be mounted from Windows systems.

How to reproduce it:
We use an on-premise Kubernetes cluster running Windows as well as Linux nodes. We have installed the kubectl csi-driver-smb-v0.6.0 in the kube-system namespace, with Windows integration enabled.

In addition, we have created a Storage class and PV/PVCs according to the following templates:

StorageClass

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: mount-readwritemany
mountOptions:
  - dir_mode=0777
  - file_mode=0777
parameters:
  createSubDir: 'false'
  csi.storage.k8s.io/node-stage-secret-name: mount-secret
  csi.storage.k8s.io/node-stage-secret-namespace: default
  source: \\10.33.3.1\share
provisioner: smb.csi.k8s.io
reclaimPolicy: Retain
volumeBindingMode: Immediate

PVC

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: iis-log-web-pvc
  namespace: default
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 100Gi
  storageClassName: mount-readwritemany

Deployment

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
  namespace: default
spec:
  replicas: 2
  selector:
    matchLabels:
      app: web
  strategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: web
      name: web
    spec:
      containers:
        - image: 'webserver:v1'
          name: web
          volumeMounts:
            - mountPath: 'C:\inetpub\logs\LogFiles\W3SVC1'
              name: iis-log-web
      nodeSelector:
        kubernetes.io/os: windows
      volumes:
        - name: iis-log-web
          persistentVolumeClaim:
            claimName: iis-log-web

Anything else we need to know?:
Windows Event Log


WinDbg

Environment:

• CSI Proxy version: v0.2.2
• CSI Driver version: v0.6.0
• Kubernetes version: v1.19.10
• OS: Windows Server 2019 Datacenter, Version 1809, OS Build 17763.1817

[andyzhangx]

have you installed csi-proxy? I am surprised that this driver would make blue screen, it just does mount & unmount through csi-proxy, below are the windows node version we are using in e2e test, it works well:

NAME                    STATUS   ROLES    AGE     VERSION    INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION     CONTAINER-RUNTIME
2046k8s000              Ready    agent    9m31s   v1.18.17   10.240.0.35    <none>        Windows Server 2019 Datacenter   10.0.17763.1397    docker://19.3.14
2046k8s001              Ready    agent    9m32s   v1.18.17   10.240.0.4     <none>        Windows Server 2019 Datacenter   10.0.17763.1397    docker://19.3.14

[WangMosquito]

yes, i have installed csi-proxy, but not die immediately, can Working for one to two days.

install to C:\etc\kubernetes\node\bin

Invoke-WebRequest https://kubernetesartifacts.azureedge.net/csi-proxy/v0.2.2/binaries/csi-proxy.tar.gz -OutFile C:\etc\kubernetes\node\bin\csi-proxy.tar.gz; 

csi-proxy.exe installed and run as binary or run as a Windows service on each Windows node

sc create csiproxy binPath="C:\etc\kubernetes\node\bin\csi-proxy.exe -windows-service -log_file=C:\etc\kubernetes\logs\csi-proxy.log -logtostderr=false"
sc failure csiproxy reset= 0 actions= restart/10000
sc start csiproxy

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.